Unable to get discovery working (Linux)

egandt · July 23, 2019, 1:40am

I have the client on a box 10.120.25.1(servera) and the server running in a docker container on 10.120.25.62(serverb) using --net “host”

On servera I start the client:
root@servera:~# urbackupclientbackend -v debug
2019-07-22 21:25:08: SQLite: recovered 25 frames from WAL file
/usr/local/var/urbackup/backup_client.db-wal code: 283
2019-07-22 21:25:08: urbackupserver: Server started up successfully!
2019-07-22 21:25:08: FileSrv: Binding UDP socket at port 35622…
2019-07-22 21:25:08: FileSrv: done.
2019-07-22 21:25:08: FileSrv: Servername: -servera-
2019-07-22 21:25:08: FileSrv: Server started up successfully
2019-07-22 21:25:08: FileSrv: UDP Thread startet
2019-07-22 21:25:08: Started UrBackupClient Backend…
2019-07-22 21:25:09: Looking for old Sessions… 0 sessions
2019-07-22 21:25:09: Internet mode not enabled
2019-07-22 21:25:09: Final path: /

Now I know that urbackup server is running as I was able to connect from a localhost to create a backup and using netstat I can see it listening:
tcp 0 0 0.0.0.0:35621 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:35623 0.0.0.0:* LISTEN
tcp 0 0 serverb:35623 serverb:52302 ESTABLISHED
tcp 0 0 serverb:52302 serverb:35623 ESTABLISHED
udp 0 0 0.0.0.0:35622 0.0.0.0:*
udp 0 0 serverb:35623 0.0.0.0:*

Also: I know udp is working: servera->serverb
root@servera:~# nc -z -v -u 10.120.25.62 35623
Connection to 10.120.25.62 35623 port [udp/] succeeded!
root@servera:~# nc -z -v -u 10.120.25.62 35622
Connection to 10.120.25.62 35622 port [udp/] succeeded!

In reverse: serverb->servera
root@serverb:~$ nc -z -v -u 10.120.25.1 35622
Connection to 10.120.25.1 35622 port [udp/*] succeeded!

So UDP works both directions, which is good to know when I ping the client I see:
2019-07-22 21:28:39: WARNING: Unknown UDP packet id
2019-07-22 21:28:39: WARNING: Unknown UDP packet id
2019-07-22 21:28:40: WARNING: Unknown UDP packet id
2019-07-22 21:28:41: WARNING: Unknown UDP packet id
2019-07-22 21:28:42: WARNING: Unknown UDP packet id

Finally: TCP connects: servera->serverb
root@servera:~# nc -z -v 10.120.25.62 55413
Connection to 10.120.25.62 55413 port [tcp/] succeeded!
root@servera:~# nc -z -v 10.120.25.62 55414
Connection to 10.120.25.62 55414 port [tcp/] succeeded!
root@servera:~# nc -z -v 10.120.25.62 35621
Connection to 10.120.25.62 35621 port [tcp/] succeeded!
root@servera:~# nc -z -v 10.120.25.62 35623
Connection to 10.120.25.62 35623 port [tcp/] succeeded!

So why can I not discover the servera from serverb, yet serverb can discover serverb so we know the urbackup server it is up and working. All ports are open and connections work both udp and tcp (though I’m confused by 35622, as I thought it was 35623) and 35623 definitely does not work to servera only to serverb . Also 35621 and 35623 are tcp and not udp on serverb, see netsta results above.

I also tried a Windows client (virtual mahcine) and that was able to connect to the serverb, though it seems hung indexing.

I’m lost as to what could be wrong or blocking discovery of servera. I tried to use the http server “add client” option also without success. I’ve waited as long as 2 hours for discovery to complete and it never happens. It seems as if there is some other port/ports I need to allow which are not documented anywhere, but I can not figure out what they would even be, and I have no FW run blocking any connections between these hosts.

While at it the client can I tell it to bind to only a single adapter if there are multiple ones present, if so how?

Thanks,
ERIC

alex · July 23, 2019, 5:17am

you can try to Setting Network Card to Hybrid Mode

egandt · July 23, 2019, 11:51am

Worked it out, I’m sure this is too open, but it is working.
Ports 55413 - 55415 TCP
Port 35621 TCP/UDP
Port 35622 UDP/TCP
Port 35623 TCP/UDP

The first is the one I think is needed, but I could not be sure so I ended up allowing both to get it finally functional.

Also not sure if I need any of the 55413-55415 ports for this, need to try restricting those again.

ERIC

equbex · July 29, 2019, 6:55pm

If you want to be precise (well, as precise as I am … not sure if mine is) you need to open
port 35621/tcp
port 35622/udp
port 35623/tcp

and you should be good to go. That is what I have on my Linux clients.
On the server I have
port 35621/tcp
port 35623/udp
port 55414-55415/tcp

We are not far off each other.

Chin chin

tfmeier · September 16, 2024, 2:48pm

I also cant discover my Linux client on Fedora.

The server is running

root@acer-bkp-server:~# sudo systemctl status  urbackup-server.service
● urbackup-server.service - UrBackup Client/Server Network Backup System
     Loaded: loaded (/usr/lib/systemd/system/urbackup-server.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Tue 2024-09-17 00:40:15 AEST; 2s ago
   Main PID: 1204 (urbackupsrv)
      Tasks: 22
     Memory: 5.4M (peak: 6.1M)
        CPU: 170ms
     CGroup: /system.slice/urbackup-server.service
             └─1204 /usr/bin/urbackupsrv run --config /etc/sysconfig/urbackup-server --no-consoletime

Sep 17 00:40:15 acer-bkp-server systemd[1]: Started urbackup-server.service - UrBackup Client/Server Network Backup Sys>
Sep 17 00:40:15 acer-bkp-server urbackupsrv[1210]: Backupfolder not set
Sep 17 00:40:15 acer-bkp-server urbackupsrv[1213]: Backupfolder not set

The client seems to be running as well

root@dell-kvmhost:~# sudo systemctl status urbackupclientbackend.service
● urbackupclientbackend.service - UrBackup Client backend
     Loaded: loaded (/usr/lib/systemd/system/urbackupclientbackend.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Tue 2024-09-17 00:26:12 AEST; 12min ago
   Main PID: 134080 (urbackupclientb)
      Tasks: 10 (limit: 23799)
     Memory: 3.8M (peak: 4.1M)
        CPU: 34ms
     CGroup: /system.slice/urbackupclientbackend.service
             └─134080 /usr/local/sbin/urbackupclientbackend --config /etc/sysconfig/urbackupclient --no-consoletime

Sep 17 00:26:12 dell-kvmhost systemd[1]: Started urbackupclientbackend.service - UrBackup Client backend.
root@dell-kvmhost:~#

The following ports are open

UrBackup client
port 35621/tcp
port 35622/udp
port 35623/tcp

UrBackup server
port 35621/tcp
port 35623/udp
port 55414-55415/tcp

I understand the client should automatically appear or do I need to use Add Client

tfmeier · September 17, 2024, 12:22am

I have some progress

Add new internet/active client which brought me to the details page on how to set it up. Done that and it got discovered.

However the client shows not online

Here’s the status of the client

root@dell-kvmhost:~# sudo systemctl status urbackupclientbackend.service
● urbackupclientbackend.service - UrBackup Client backend
     Loaded: loaded (/usr/lib/systemd/system/urbackupclientbackend.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Tue 2024-09-17 00:26:12 AEST; 9h ago
   Main PID: 134080 (urbackupclientb)
      Tasks: 11 (limit: 23799)
     Memory: 7.3M (peak: 7.9M)
        CPU: 931ms
     CGroup: /system.slice/urbackupclientbackend.service
             └─134080 /usr/local/sbin/urbackupclientbackend --config /etc/sysconfig/urbackupclient --no-consoletime

Sep 17 00:26:12 dell-kvmhost systemd[1]: Started urbackupclientbackend.service - UrBackup Client backend.
root@dell-kvmhost:~#

Why can’t I see the status on the server?

tfmeier · September 17, 2024, 10:30am

The issue was with the setup of ports. After making sure this is setup correctly for both client and server the client became available