No connection with Linux client (2.0.34)

Hi,

Today I’ve installed Urbackup server and client on one server from one of my clients. This is the first time I have problems with urbackup server trying to detect the client installed in the same machine (name/host ‘patalibro’).

Urbackup srv log:

2016-11-01 09:44:21: Starting HTTP-Server on port 55414
2016-11-01 09:44:21: HTTP: Server started up successfully!
2016-11-01 09:44:21: SQLite: recovered 3 frames from WAL file /var/urbackup/backup_server.db-wal code: 283
2016-11-01 09:44:21: SQLite: recovered 1 frames from WAL file /var/urbackup/backup_server_link_journal.db-wal code: 283
2016-11-01 09:44:21: SQLite: recovered 11 frames from WAL file /var/urbackup/backup_server_settings.db-wal code: 283
2016-11-01 09:44:21: Started UrBackup…
2016-11-01 09:44:21: Removing temporary files…
2016-11-01 09:44:21: Recreating temporary folder…
2016-11-01 09:44:21: Testing if backup destination can handle subvolumes and snapshots…
2016-11-01 09:44:21: Backup destination cannot handle subvolumes and snapshots. Snapshots disabled.
2016-11-01 09:44:21: Testing if backup destination can handle filesystem transactions…
2016-11-01 09:44:21: Binding to interface eno4 for broadcasting…
2016-11-01 09:44:21: Broadcasting on interface IP 192.168.1.3
2016-11-01 09:44:22: UrBackup Server start up complete.
2016-11-01 09:44:22: Looking for old Sessions… 0 sessions
2016-11-01 09:44:22: Server started up successfully!
2016-11-01 09:44:51: HTTP: No available slots… starting new Worker
2016-11-01 09:44:53: New Backupclient: patalibro
2016-11-01 09:44:53: Sending Identity to client “patalibro” failed. Retrying soon…
2016-11-01 09:45:21: Downloading version file…
2016-11-01 09:45:23: Downloading version file…
2016-11-01 09:45:24: Downloading version file…
2016-11-01 09:45:25: Downloading server version info…

Urbackup client log:

2016-11-01 09:42:42: urbackupserver: Server started up successfully!
2016-11-01 09:42:42: FileSrv: Binding UDP socket at port 35622…
2016-11-01 09:42:42: FileSrv: done.
2016-11-01 09:42:42: FileSrv: Servername: -patalibro-
2016-11-01 09:42:42: FileSrv: Server started up successfully
2016-11-01 09:42:42: FileSrv: UDP Thread startet
2016-11-01 09:42:42: Started UrBackupClient Backend…
2016-11-01 09:42:43: Looking for old Sessions… 0 sessions
2016-11-01 09:42:43: Internet mode not enabled
2016-11-01 09:43:53: urbackupserver: No available slots… starting new Worker
2016-11-01 09:43:53: ClientService cmd: #ILzHtuVVzc7HSl770EFBz#ADD IDENTITY
2016-11-01 09:43:53: rc=0 hasError=true state=0
2016-11-01 09:45:43: Internet mode not enabled

Both logs are in debug mode.

Server version: 2.0.36
Client version: 2.0.34
OS: Ubuntu 16.04.1 LTS

Any ideas?

Thanks in advance.

Are you saying you are running the client and server on the same physical machine?

Yes, Like the other servers I have (which includes one of my own, same OS version and I don’t have this problem. All the others servers which I’ve tested have Ubuntu 14.04).

But I can’t figure it out what is causing it. Already installed server and clients apps from scratch…

Thanks.

EDIT: also, I guess the problem is in this info on the server log:

2016-11-01 09:44:53: New Backupclient: patalibro
2016-11-01 09:44:53: Sending Identity to client “patalibro” failed. Retrying soon…

Have you tried to remove the client software from the client and then download the preconfigured client software from the server web interface?
This eliminates any typos / user confit errors.

The problem is that the clients is not being detected (problems with the
Identity, like the logs indicates it). I’ve tried to reinstall the client,
deleting the keys from server_key.txt (like tha faq points to it:
https://www.urbackup.org/faq.html#ident_err), located in
/usr/local/var/urbackup, but the problem still persist.

Any ideas?

Thanks.

Gustavo A. Díaz
GDNet - www.gdnet.com.ar
“Servicios TI para tus necesidades”
Tel. (011) 2063-8252
Cel. 15-6469-7064

Hi, any ideas about this problem?

Thanks in advance.

Well… I’ve just fixed… my Client left a old UrBackup server turned on on the same network and this was causing the problem.

Thanks.