Client not connecting after removing (re-adding clients)

client
1

Hey UrBackup-Community,

I have problems regarding my UrBackup server running in a local network. On the same machine I installed a client in order to back it up (64-bit Debian). Because of some problems I had to re-add the client.
So I removed the client and tried to re-add it. But now the status of the client stays in “internet_status” = “wait_local” (switches to “no_server” after some minutes) and “internet_connected” = false.
It seems like the client is blacklisted after being removed.
Flushing the database didn’t help.

How can I re-add the client running on the same machine?
The “add client” function doesn’t work and the client is not discovered by the server.
Is there a way to manually add the client? Or can I “unblock” the client?

The server client says:
2018-09-14 15:46:25: ERROR: urbackupserver: Failed binding socket to port 35623. Another instance of this application may already be active and bound to this port.
2018-09-14 15:46:25: ERROR: Binding tcp socket to port 35621 failed. Another instance of this application may already be active and bound to this port.

But I’m not sure if it is related to my problem.

Also the log is spammed with these error messages:
2018-09-11 21:36:47: ERROR: Token id for group “staff” not found
2018-09-11 21:36:47: ERROR: Token id for group “games” not found
2018-09-11 21:36:47: ERROR: Token id for group “users” not found
2018-09-11 21:36:47: ERROR: Token id for group “nogroup” not found
2018-09-11 21:36:47: ERROR: Token id for group “systemd-journal” not found
2018-09-11 21:36:47: ERROR: Token id for group “systemd-timesync” not found
2018-09-11 21:36:47: ERROR: Token id for group “systemd-network” not found
2018-09-11 21:36:47: ERROR: Token id for group “systemd-resolve” not found
2018-09-11 21:36:47: ERROR: Token id for group “systemd-bus-proxy” not found
2018-09-11 21:36:47: ERROR: Token id for group “input” not found
2018-09-11 21:36:47: ERROR: Token id for group “crontab” not found
2018-09-11 21:36:47: ERROR: Token id for group “Debian-exim” not found
2018-09-11 21:36:47: ERROR: Token id for group “messagebus” not found
2018-09-11 21:36:47: ERROR: Token id for group “ssh” not found
2018-09-11 21:36:47: ERROR: Token id for group “ssl-cert” not found
2018-09-11 21:36:47: ERROR: Token id for group “postfix” not found
2018-09-11 21:36:47: ERROR: Token id for group “postdrop” not found
2018-09-11 21:36:47: ERROR: Token id for group “rdma” not found
2018-09-11 21:36:47: ERROR: Token id for group “ceph” not found
2018-09-11 21:36:47: ERROR: Token id for group “ntp” not found

But these messages don’t occur right now. They happened 3 days ago…

These messages also appear multiple times in the log:
2018-09-14 16:11:42: ERROR: Error getting Client settings of MBP.localdomain. Errorcode: BASE_DIR_LOST (7)
2018-09-14 16:11:42: ERROR: Getting client settings failed -2

I think these messages occur because the client is listed in the web-interface but the client is not even installed on the machine (MBP.localdomain).

These are my versions:
root@vhost:~# urbackupclientbackend --version
UrBackup Client Backend v2.2.6.0
Copyright © 2011-2018 Martin Raiber
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

root@vhost:~# urbackupsrv --version
UrBackup Server v2.2.11.0
Copyright © 2011-2018 Martin Raiber
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Is there a possibility to completely un-install both - the client and server and re-install it completely fresh? So it also can be configured from start of.

It’s really frustrating and pretty complicated if you’re not too deep in development and administration.
I hope you can help me!

Greetings,
Luca

2

This is a very “Windows Admin” answer to a Linux problem… but between removing & re-adding I’d strongly recommend a reboot, it’ll free up the sockets the client was bound to, which may not “just happen” by itself… and I’m not a good enough Linux admin to supply you a command to do it… well… other than systemctl reboot

3

Thanks for your fast answer! Unfortunately rebooting did not solve my problem. It’s still the same scenario like before :slightly_frowning_face:

4

Don’t think I can add much else, my experience with UrBackup is entirely under Windows. It was the failed to bind to socket messages that made me think a reboot might fix it, I’ve seen that issue with other Linux server applications.

If you’re trying to get backups running again from a machine where you uninstalled the client, I’d suggest accessing the server webpage from that client machine, logging in & picking “download preconfigured client”, if you removed the client on the server end I’d expect it to just be found again as a new client.

5

Oh I forgot to mention that I use the command-line version since it’s a bigger hostsystem.

6

This most likely means that you already have a client backend running and you try to run another.
Another low probability is that a different app use th same ports

7

How can I check that? Is there a possibility to wipe all the UrBackup installations and just start from the beginning? I would appreciate that and it would be possible since I didn’t backup anything yet.

8

Hello.
You can check run urbackupclinet on the linux machine with command
sudo systemctl status urbackupclientbackend.service.
and look urbackupclient is runing or not. If urbackupclinet is not runing, you can run it with commands
sudo systemctl restart urbackupclientbackend.service.