Last Sunday, I updated my home UrBackup server to 2.4.9 (on Debian Buster). Since then, most of my clients (all Linux, mostly Debian) have stopped working. I’ve just updated to 2.4.10 about 30 minutes ago as I try to solve the problem, but this didn’t help.
The clients that did remain working are all still running older versions of the client - 2.3.4 and 2.1.15. All the ones listed as 2.4.8 are failed.
Also notable is that all the failed 2.4.8 clients are showing up under different names in the server… Previously, most clients were listed as their FQDN (which I prefer), but the failed ones have all been duplicated. They now show up as a short hostname instead, with a different backup set for each entry. Yes, both come up as offline.
I have got one of the clients to start working again. After updating the server to 2.4.10, I found an old 2.2.6 installer on the client I was fiddling with. Since it was a client-specific installer downloaded from my server for that client, I figured it couldn’t hurt, and installed it… This allowed the client to reconnect (using it’s old FQDN name) and start a backup. However, the client then suddenly went offline again.
It turns out the client updated itself to 2.4.8 again. I had turned off automatic updates, so this was a little surprising, however I manually restarted the client (it failed to start after the update), and it appears to be working OK again.
I guess my question now is… What do I do with the other 15 or so failed clients? Should I go through one by one downloading the custom installer for each client?