Debian 11 Server 2.5.26.0-1
Debian 11 client with client modules fresh downloaded (pulled) from server
If I start the urbackupclientbackend it crashes 1 minute later with:
root@pve:/root# systemctl status urbackupclientbackend
ā urbackupclientbackend.service - UrBackup Client backend
Loaded: loaded (/lib/systemd/system/urbackupclientbackend.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Thu 2022-09-29 14:24:20 CEST; 9s ago
Process: 1997237 ExecStart=/usr/local/sbin/urbackupclientbackend --config /etc/default/urbackupclient --no-consoletime (code=killed, signal=SEGV)
Main PID: 1997237 (code=killed, signal=SEGV)
CPU: 1.525s
Sep 29 14:23:52 pve urbackupclientbackend[1997318]: No LSB modules are available.
Sep 29 14:24:17 pve urbackupclientbackend[1997237]: Final path: /mnt/pve/backup/backups/proxmox
Sep 29 14:24:17 pve urbackupclientbackend[1997237]: Script list at "/usr/local/etc/urbackup/scripts/list" does not exist. Skipping.
Sep 29 14:24:17 pve urbackupclientbackend[1997237]: Deleting files... doing full index...
Sep 29 14:24:17 pve urbackupclientbackend[1997237]: Final path: /mnt/pve/backup/backups/proxmox
Sep 29 14:24:17 pve urbackupclientbackend[1997237]: Backing up "proxmox" without snapshot.
Sep 29 14:24:17 pve urbackupclientbackend[1997237]: Indexing of "proxmox" done. 1 filesystem lookups 0 db lookups and 0 db updates
Sep 29 14:24:20 pve systemd[1]: urbackupclientbackend.service: Main process exited, code=killed, status=11/SEGV
Sep 29 14:24:20 pve systemd[1]: urbackupclientbackend.service: Failed with result 'signal'.
Sep 29 14:24:20 pve systemd[1]: urbackupclientbackend.service: Consumed 1.525s CPU time.
root@pve:/root#
Has anybody an idea why this happens? All our other Debian11 clients are working properly.