Client does not do any Backups

A single Linux client out of a long list fails to do any backups.

The status page of the server says that the client is indexing, but it never finishes.

infnite_indexing

urbackupclientctl status does not show any running backup processes.
It is an internet/active client and was installed using the automatically created installer from the webui.

I recently uninstalled the existing client and installed again using a newly created installer with a different client name but the behavior is the exact same.

The life-protocol on the server only shows the loading-spinner and no text what so ever.


Trying to manually start a file backup from the client results in the client hanging on preparing (the spinner animation eventually stops),

hang_on_prepare
but the server seems to see the client when online and vice versa.

online_yes

Are you getting the live log for other clients?

Could you enable debug logging on the client and post/send the log? See here on instructions how to do this: Having problems with UrBackup? Please read before posting

In case it helps with getting uroni the debug log on Linux:

  1. In /etc/default/urbackupclient (/etc/sysconfig/urbackupclient on RHEL-type distros), set LOGLEVEL=debug
  2. systemctl restart urbackupclientbackend
  3. Start a backup, wait until it’s stuck on indexing, and grab /var/log/urbackupclient.log

Something worth checking while it’s stuck: before indexing, the Linux client runs a filesystem snapshot script (dattobd, LVM, btrfs or device-mapper, whichever the installer set up) and waits for it to finish, with no timeout. If that script hangs, indexing never ends and there’s often nothing in the log. That would also explain why reinstalling with a new client name didn’t help, since the snapshot configuration survives a reinstall.

  • cat /usr/local/etc/urbackup/snapshot.cfg shows which method it uses
  • ps -ef | grep -E "snapshot|dattobd|lvcreate" shows whether a snapshot process is stuck
  • If it’s dattobd and the kernel was updated recently, check that the module still loads (lsmod | grep dattobd)