Tape Backups Fail After Upgrade to PBS 3.2-4.

[BriBriBri]

Tape backup jobs now fail since upgrading to pbs 3.2-4 last week:

2024-06-22T14:00:00-07:00: waiting for drive lock...
2024-06-22T14:00:00-07:00: Starting tape backup job 'pbs2-primary-140tb:pve-tapes:lto8:weekly-tape-backup'
2024-06-22T14:00:00-07:00: task triggered by schedule 'sat 14:00'
2024-06-22T14:00:00-07:00: update media online status
2024-06-22T14:00:01-07:00: starting new media set - reason: policy is AlwaysCreate
2024-06-22T14:00:01-07:00: media set uuid: (redacted)
2024-06-22T14:00:01-07:00: found 129 groups (out of 129 total)
2024-06-22T14:00:01-07:00: latest-only: true (only considering latest snapshots)
2024-06-22T14:00:01-07:00: backup snapshot "ns/baremetal/host/moment01/2024-06-22T05:00:01Z"
2024-06-22T14:00:01-07:00: allocated new writable media 'ATT012L8'
2024-06-22T14:00:01-07:00: trying to load media 'ATT012L8' into drive 'lto8'
2024-06-22T14:01:55-07:00: tape read failed - command "/usr/lib/x86_64-linux-gnu/proxmox-backup/sg-tape-cmd" "encryption" "--stdin" "--fingerprint" "redacted-for-sheer-paranoia" "--uuid" "redacted-for-sheer-paranoia" failed - status code: 1 - Error: this program needs to be run with setuid root

2024-06-22T14:01:55-07:00: Please insert media 'ATT012L8' into changer 'superloader'

Not doing anything special or out of the ordinary. Nothing tweaked or strange. Worked fine until updates were applied last week.

("redacted" in the above is by me. . . even though it wasn't necessary!)

Though we're subscribed for 13 nodes of proxmox, we haven't yet subscribed for pbs. We're on the non-sub repo and the version of pbs is 3.2-4.

--Brian

(there's a thread in the pbs german forum about this but I thought it might be a good idea to post here as well)

 

[BriBriBri]

can't even load a tape and format it. Get same "Error: this program needs to be run with setuid root" as above.

 

[dcsapak]

what does the following command show?

ls -lh /usr/lib/x86_64-linux-gnu/proxmox-backup/*

 

[BriBriBri]

Hello dcsapak,

As requested:

root@pbs2:~# ls -lh /usr/lib/x86_64-linux-gnu/proxmox-backup/*
-rwxr-xr-x 1 root root  27M Jun  5 07:23 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-api
-rwxr-xr-x 1 root root 427K Jun  5 07:23 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-banner
-rwxr-xr-x 1 root root  29M Jun  5 07:23 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy
-rwxr-xr-x 1 root root 9.2M Jun  5 07:23 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-daily-update
-rwxr-xr-x 1 root root 2.3M Jun  5 07:23 /usr/lib/x86_64-linux-gnu/proxmox-backup/sg-tape-cmd

 

[dcsapak]

ok the error seems to be cause by the sg-tape-cmd binary. this should have the 'setuid' bit set e.g. here it is:

-rwsr-xr-x 1 root root 2.3M Jun 17 10:18 /usr/lib/x86_64-linux-gnu/proxmox-backup/sg-tape-cmd

notice the '-rws' at the beginning while you have '-rwx'

i cannot tell why that happened, but it should be fixed if you reinstall the pacakge 'proxmox-backup-server'

with

apt install --reinstall proxmox-backup-server

that should fix all wrong permissions/file modes/missing/wrong files for that package

alternatively you could set the 'setuid' bit manually for that file:

chmod +s /usr/lib/x86_64-linux-gnu/proxmox-backup/sg-tape-cmd

 

[Mister X]

Same error. Also a reinstall does'nt resolve it.

Manually set the uid works.

 

[dcsapak]

ok sorry just noticed the answer from a colleague, it seems to be a problem with that specific version of proxmox-backup-server:
https://forum.proxmox.com/threads/p...2-4-1-tape-jobs-format-and-write-fail.149383/

the version before and after should be fine, so you could just manually set the bit like i described above, and future updates should be fine again

 

[BriBriBri]

Thank you, dcsapak. setuid bit set as you described. Tape backup job is now running.