Upgrade to 2.0.1

[taich]

I just upgraded my Backup-Server from 1.1.11 to 2.0 as described in wiki.
https://pbs.proxmox.com/wiki/index.php/Upgrade_from_1.1_to_2.x

After reboot the Proxmox Backup Services do not start any more.

Here's the log:

systemctl status proxmox-backup-proxy.service proxmox-backup.service
● proxmox-backup-proxy.service - Proxmox Backup API Proxy Server
     Loaded: loaded (/lib/systemd/system/proxmox-backup-proxy.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2021-10-27 15:25:02 CEST; 9min ago
    Process: 1250 ExecStart=/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy (code=exited, status=127)
   Main PID: 1250 (code=exited, status=127)
        CPU: 1ms


Oct 27 15:25:02 pbs systemd[1]: proxmox-backup-proxy.service: Scheduled restart job, restart counter is at 5.
Oct 27 15:25:02 pbs systemd[1]: Stopped Proxmox Backup API Proxy Server.
Oct 27 15:25:02 pbs systemd[1]: proxmox-backup-proxy.service: Start request repeated too quickly.
Oct 27 15:25:02 pbs systemd[1]: proxmox-backup-proxy.service: Failed with result 'exit-code'.
Oct 27 15:25:02 pbs systemd[1]: Failed to start Proxmox Backup API Proxy Server.


● proxmox-backup.service - Proxmox Backup API Server
     Loaded: loaded (/lib/systemd/system/proxmox-backup.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Wed 2021-10-27 15:25:46 CEST; 8min ago
    Process: 1272 ExecStart=/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-api (code=exited, status=127)
   Main PID: 1272 (code=exited, status=127)
        CPU: 1ms


Oct 27 15:25:46 pbs systemd[1]: proxmox-backup.service: Scheduled restart job, restart counter is at 5.
Oct 27 15:25:46 pbs systemd[1]: Stopped Proxmox Backup API Server.
Oct 27 15:25:46 pbs systemd[1]: proxmox-backup.service: Start request repeated too quickly.
Oct 27 15:25:46 pbs systemd[1]: proxmox-backup.service: Failed with result 'exit-code'.
Oct 27 15:25:46 pbs systemd[1]: Failed to start Proxmox Backup API Server.

Is there any idea why?

 

[dcsapak]

The complete journal since boot would be interesting: 'journalctl -b' (this will contain more lines and probably show the problem)

 

[taich]

What is this lib (libsgutils2.so.2) good for?

Oct 27 15:23:47 pbs systemd[1]: Starting Proxmox Backup API Server...
Oct 27 15:23:47 pbs rpc.mountd[949]: Version 1.3.3 starting
Oct 27 15:23:47 pbs proxmox-backup-api[948]: /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-api: error while loading shared libraries: libsgutils2.so.2: cannot open shared object file: No such file or directory
Oct 27 15:23:47 pbs systemd[1]: Started fast remote file copy program daemon.
Oct 27 15:23:47 pbs systemd[1]: Stopped System Logging Service.
Oct 27 15:23:47 pbs systemd[1]: Starting System Logging Service...
Oct 27 15:23:47 pbs systemd[1]: Starting OpenBSD Secure Shell server...
Oct 27 15:23:47 pbs systemd[1]: Started NFS Mount Daemon.
Oct 27 15:23:47 pbs systemd[1]: proxmox-backup.service: Main process exited, code=exited, status=127/n/a
Oct 27 15:23:47 pbs systemd[1]: proxmox-backup.service: Failed with result 'exit-code'.
Oct 27 15:23:47 pbs systemd[1]: Failed to start Proxmox Backup API Server

 

[t.lamprecht]

What is this lib (libsgutils2.so.2) good for?

it's a SCSI Generic utils library and used by the tape part of the backup server.

Oct 27 15:23:47 pbs proxmox-backup-api[948]: /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-api: error while loading shared libraries: libsgutils2.so.2: cannot open shared object file: No such file or directory

Seems to me the upgraded wasn't a complete success, are you sure that you have valid Debian and Proxmox Backup Server repositories configured?

Can you please also post the output of the following three commands to see if there's something to spot in that direction:

head -n -0 /etc/apt/sources.list /etc/apt/sources.list.d/*
apt update
proxmox-backup-manager versions --verbose

 

[taich]

This solved it:

cd /usr/lib/x86_64-linux-gnu/
ln -s libsgutils2-1.45.so.2.0.0 libsgutils2.so.2

 

[t.lamprecht]

This solved it:

cd /usr/lib/x86_64-linux-gnu/
ln -s libsgutils2-1.45.so.2.0.0 libsgutils2.so.2

That's fighting symptoms, and if the update was done properly such things are not required and other things can still go bad..

 

[taich]

it's a SCSI Generic utils library and used by the tape part of the backup server.


Seems to me the upgraded wasn't a complete success, are you sure that you have valid Debian and Proxmox Backup Server repositories configured?

Can you please also post the output of the following three commands to see if there's something to spot in that direction:

head -n -0 /etc/apt/sources.list /etc/apt/sources.list.d/*
apt update
proxmox-backup-manager versions --verbose

==> /etc/apt/sources.list <==
deb http://ftp.at.debian.org/debian bullseye main contrib

deb http://ftp.at.debian.org/debian bullseye-updates main contrib

# security updates
deb http://security.debian.org bullseye-security main contrib

==> /etc/apt/sources.list.d/pbs-enterprise.list <==
deb https://enterprise.proxmox.com/debian/pbs bullseye pbs-enterprise

==> /etc/apt/sources.list.d/pve-no-subscription.list <==
deb http://download.proxmox.com/debian/pve buster pve-no-subscription

proxmox-backup-manager versions --verbose
proxmox-backup             1.0-4              running kernel: 5.4.143-1-pve
proxmox-backup-server      1.1.1-1            running version: 1.1.1       
pve-kernel-helper          6.4-8                                           
pve-kernel-5.4             6.4-7                                           
pve-kernel-5.4.143-1-pve   5.4.143-1                                       
pve-kernel-5.4.140-1-pve   5.4.140-1                                       
pve-kernel-5.4.106-1-pve   5.4.106-1                                       
ifupdown2                  3.0.0-1+pve4~bpo10                              
libjs-extjs                6.0.1-10                                        
proxmox-backup-docs        1.1.1-1                                         
proxmox-backup-client      1.1.13-2                                        
proxmox-mini-journalreader 1.1-1                                           
proxmox-widget-toolkit     2.6-1                                           
pve-xtermjs                4.7.0-3                                         
smartmontools              7.2-pve2                                        
zfsutils-linux             2.0.6-pve1~bpo10+1

 

[t.lamprecht]

Is this a host with both Proxmox VE and Proxmox Backup Server installed? As you have a Debian Bullseye, Proxmox Backup Server Bullseye (2.x) but PVE Buster (6.x) repo configured, which is probably the cause of holding lots of packages back.

deb http://download.proxmox.com/debian/pve buster pve-no-subscription

That one needs to either change from buster to bullseye or removed completely if no PVE is co-installed, then check also
https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0#In-place_upgrade
and you should be able to actually upgrade.

 

[taich]

Just a backup server
I did not change /etc/apt/sources.list.d/pve-no-subscription.list

There was still buster.

 

[t.lamprecht]

I did not change /etc/apt/sources.list.d/pve-no-subscription.list

It needs to come from somewhere and our packages definitively do not set that list file anywhere...

Any how if you're really sure that there's no PVE on this system (maybe try pveversion -v) then you can simply rm this file and re-do a full-upgrade, e.g., something along:

rm /etc/apt/sources.list.d/pve-no-subscription.list
apt update
apt full-upgrade

But as said, please double check first, we want to get out of this mess not dig in deeper after all

 

[taich]

I just installed another new backup server 2.x and there you also find the pve-no-subscribtion with buster entry. I think the update as described here (https://pbs.proxmox.com/wiki/index.php/Upgrade_from_1.1_to_2.x) does not work.

I am going to do a fresh install now.

 

[abma]

pbs 2.x requires debian 11 / bullseye: you have to adjust sources.list:

https://pbs.proxmox.com/wiki/index.php/Upgrade_from_1.1_to_2.x#Actions_step-by-step

which you don't have it seems.

I upgraded debian 10 + pbs 1.x to debian 11 + pbs 2.x with the given instructions and they worked very well for me.


this file is wrong for debian bullseye and very likely the cause of your problems:

==> /etc/apt/sources.list.d/pve-no-subscription.list <==
deb http://download.proxmox.com/debian/pve buster pve-no-subscription

 

[t.lamprecht]

I just installed another new backup server 2.x and there you also find the pve-no-subscribtion with buster entry.

How did you install it? Searching for that file via the dpkg tool (which can match any file that comes from a package) results in zero matches, see yourself:

dpkg -S /etc/apt/sources.list.d/pve-no-subscription.list
dpkg-query: no path found matching pattern /etc/apt/sources.list.d/pve-no-subscription.list

Whereas searching for a file that we actually ship, namely pbs-enterprise.list turns up some results:

dpkg -S /etc/apt/sources.list.d/pbs-enterprise.list     
proxmox-backup-server: /etc/apt/sources.list.d/pbs-enterprise.list

FWIW: I installed dozens, if not hundreds, of PBS instances via our official ISO or on top of Debian for testing and production purposes, and never run into seeing a random no-subscription repo for a completely different product pop up, if you see that please check your installation medium, it seems broken or at least not official..

I think the update as described here (https://pbs.proxmox.com/wiki/index.php/Upgrade_from_1.1_to_2.x) does not work.

They work quite well, we got lots of positive feedback here in the forum and on other channels. If a user configures bogus repos and then does not want to follow the steps proposed to solve that it's hard to get it right...

 

[taich]

Ok I messed it up. Anyway after I installed the new Backup Server 2.04 it's working again now.

 

[djdonnerwolke]

This solved it:

cd /usr/lib/x86_64-linux-gnu/
ln -s libsgutils2-1.45.so.2.0.0 libsgutils2.so.2

This solution also worked for me.
Now the api works again.
Now I can log in to the web interface, but I still see version 1.1.1 in the web interface. And the web interface does not work after logging in. I can't do anything. This means that I can make my backups but I can no longer do any configuration in the web interface.
For me, everything is up to date and I have installed the server over it again. Is there any other idea?
If any data is needed, I am happy to provide it.
I wish you a good start into the new week.
Thank you.