Failed to install urbackup-client on Ubuntu 18 LTS Server

client
1

I have tried to install the most recent Urbackup Client with the following command:

TF=\`mktemp\` && wget "https://hndl.urbackup.org/Client/2.4.8/UrBackup%20Client%20Linux%202.4.8.sh" -O $TF && sudo sh $TF; rm -f $TF

It fails with the following messages:
Verifying archive integrity… All good.
Uncompressing UrBackup Client Installer for Linux 100%
Installation of UrBackup Client 2.4.8 to /usr/local … Proceed ? [Y/n]

Uncompressing install data…
Detected Debian (derivative) system
Detected systemd
Detected architecture x86_64-linux-glibc
(Glibc not installed or too old (2). Falling back to Android NDK build…)
Illegal instruction (core dumped)
Error running executable on this system (x86_64). Stopping installation.

I have tried the version as indicated here: [Ubuntu] Glibc not installed or too old
But the result ist the same.

I’m running Ubuntu 18 LTS server with the most current updates.

Can you please advise, what I could do?

2

Have same problem on Centos 7 lxc container (Proxmox), both privileged and unprivileged (run as root):
TF=`mktemp` && wget “https://hndl.urbackup.org/Client/2.4.8 UrBackup%20Client%20Linux%202.4.8.sh” -O $TF && sh $TF; rm -f $TF

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

Uncompressing install data...
Assuming RedHat (derivative) system
Detected systemd
Detected architecture x86_64-linux-glibc
(Glibc not installed or too old (2). Falling back to Android NDK build...)
Error running executable on this system (x86_64). Stopping installation.

When install in Centos 8 container:
Verifying archive integrity… All good.
Uncompressing UrBackup Client Installer for LinuxExtraction failed.
100% Signal caught, cleaning up

In Debian 10 lxc-container all works quite well.

3

Please take a look at the thread OP linked and try the version linked in the thread.

SIGILL usually means you CPU gets an instruction (in the linked thread SSE4 instruction) that your CPU does not support. So your excact CPU and what features it has are important (/proc/cpuinfo on Linux).

4

I managed to install version from that thread in Centos 7 container:

 TF=\`mktemp\` && wget "http://beta.urbackup.org/tmp/UrBackupUpdateLinux-dbg.sh" -O $TF && sh $TF; rm -f $TF
Verifying archive integrity... All good.
Uncompressing UrBackup Client Installer for Linux (debug)  100%  
Installation of UrBackup Client 2.4.8 to /usr/local ... Proceed ? [Y/n]
Uncompressing install data...
Assuming RedHat (derivative) system
Detected systemd
Detected architecture x86_64-linux-glibc
(Glibc not installed or too old (2). Falling back to Android NDK build...)
Installed daemon configuration at /etc/sysconfig/urbackupclient...
Info: Restoring from web interface is disabled per default. Enable by modifying /etc/sysconfig/urbackupclient.
Installing systemd unit...
Created symlink from /etc/systemd/system/multi-user.target.wants/urbackupclientbackend.service to /usr/lib/systemd/system/urbackupclientbackend.service.
Starting UrBackup Client service...
Successfully started client service. Installation complete.
+Detected EL/RH 7. Dattobd supported

-Detected no btrfs filesystem
-LVM not installed
Please select the snapshot mechanism to be used for backups:
1) dattobd volume snapshot kernel module from https://github.com/datto/dattobd
4) Use no snapshot mechanism
4
Configured no snapshot mechanism

In Centos 8 container I have same “100% Signal caught, cleaning up” error.

I don’t think the problem somewhat related to SSE4 in my case because client installs and works well on proxmox server that runs these containers. Moreover I have client installed in container with Debian 10 on same Proxmox server and it works without any struggles too.

5

Could be something with e.g. /tmp (not enough space). See Extraction failed - Client installation

Helpful info would be output of strace -f sh UrBackupUpdateLinux-dbg.sh