Linux "autoupdate" clients not updating/reports wrong version

client
1

My linux clients has not been updating since ver 2.5.23 (updated fine before that, suddenly just stopped) so today after running the server update I decided to download the latest client to one of my computers.

Downloading ver 2.5.25 but notification says 2.5.24

$ sudo systemctl stop urbackupclientbackend.service
$ TF=$(mktemp) && wget "https://hndl.urbackup.org/Client/2.5.25/UrBackup%20Client%20Linux%202.5.25.sh" -O $TF && sudo sh $TF; rm -f $TF                                                                ✔ 
--2023-10-05 13:05:29--  https://hndl.urbackup.org/Client/2.5.25/UrBackup%20Client%20Linux%202.5.25.sh
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving hndl.urbackup.org (hndl.urbackup.org)... 198.58.118.162, 2600:3c00::f03c:91ff:fec8:ecf6
Connecting to hndl.urbackup.org (hndl.urbackup.org)|198.58.118.162|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 25458401 (24M) [text/x-sh]
Saving to: ‘/tmp/tmp.7blZCYAn12’

/tmp/tmp.7blZCYAn12                                  100%[======================================================================================================================>]  24,28M  1,17MB/s    in 22s     

2023-10-05 13:05:52 (1,09 MB/s) - ‘/tmp/tmp.7blZCYAn12’ saved [25458401/25458401]

Verifying archive integrity... All good.
Uncompressing UrBackup Client Installer for Linux  100%  
Installation of UrBackup Client 2.5.24 to /usr/local ... Proceed ? [Y/n]

I acepted the install, webgui now reports ver 2.5.24 AND the other client (that was live) on this server reports same version but I’m pretty sure it did nothing there, no files are changed on that client (piServer).

But on the server side, yes, my reinstalled client was detected and added correctly:

2023-10-05 13:10:30: Client exited: bednaManjaro
2023-10-05 13:10:33: client_main Thread for client bednaManjaro finished
2023-10-05 13:11:20: Client finished: bednaManjaro
2023-10-05 13:12:10: New Backupclient: bednaManjaro
2023-10-05 13:12:11: Updated client "bednaManjaro" successfully

I sadly did not screenshot before I ran the updates, but this is now.

image
image966×177 17 KB

I very rarely ping, but this… @uroni

2

This was reported not long ago, https://forums.urbackup.org/t/clients-not-updating-to-2-5-34-any-way-to-force-client-updates (ignore the thread title, it’s a typo) I did find a way to update it then, will need to see if it’s the still the same

1 Like
3

I know, I was involved in that thread to… xD
But at that stage, I opted to not run any updates to my clients until yet another version was released to see if a solution was to come.

Today a server update was ran by me and my clients did not autoupdate. I manually reinstalled ONE of my clients and this was the result. :-S

Edit
To clarify. Before I updated my client ALL the clients in the web gui was showing 2.5.23.
I can also boot up windows and see how that client reacts, but I’d rather save that IN CASE someone who can actually give a correct answer gives feedback. Maybe it can be used for debugging to help solve this, unless the reason is already known.

4

I just tried to update from .24 to .25 using the same command but with .25:

TF=$(mktemp) && wget “https://hndl.urbackup.org/Client/2.5.25/update/UrBackupUpdateLinux.sh” -O $TF && sudo sh $TF; rm -f $TF

And a check on version still says .24:

image

I did manually stop the service before running it just in case