Random backup failure after PBS 2.2

D

da-alb

Member
Jan 18, 2021
121
3
23
Hi,

I'm using a 6.4 PVE host with 2.2 PBS host and sometimes I have this error: VM 129 qmp command 'backup' failed - backup connect failed: command error: Unable to acquire lock "/var/log/proxmox-backup/tasks/.active.lock" - Interrupted system call (os error 4).

If I do the backup manually, it works just fine. The VM is a Debian guest with guest tools installed.

PVE package version:
proxmox-ve: 6.4-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)
pve-kernel-5.4: 6.4-13
pve-kernel-helper: 6.4-13
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.166-1-pve: 5.4.166-1
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.13-1-pve: 5.3.13-1
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.5-pve2~bpo10+1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: not correctly installed
ifupdown2: 3.0.0-1+pve4~bpo10
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.22-pve2~bpo10+1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.1.13-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.3-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.7-pve1


PBS package version:
proxmox-backup: 2.2-1 (running kernel: 5.15.35-1-pve)
proxmox-backup-server: 2.2.1-1 (running version: 2.2.1)
pve-kernel-5.15: 7.2-3
pve-kernel-helper: 7.2-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.11.22-1-pve: 5.11.22-2
ifupdown2: 3.1.0-1+pmx3
libjs-extjs: 7.0.0-1
proxmox-backup-docs: 2.2.1-1
proxmox-backup-client: 2.2.1-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.5.1
pve-xtermjs: 4.16.0-1
smartmontools: 7.2-pve3
zfsutils-linux: 2.1.4-pve1

Any idea?
 
can you post the journal from the time the error occurs? e.g. from last boot: 'journalctl -b'
 
you can limit the timeframe from journalctl with '--since' and '--until' parameters, no need to attach the whole log from three days.
but you can of course upload it somewhere if you want, but please tell me around what times the error occured then..
 
dcsapak said:
you can limit the timeframe from journalctl with '--since' and '--until' parameters, no need to attach the whole log from three days.
but you can of course upload it somewhere if you want, but please tell me around what times the error occured then..
Click to expand...
PBS: https://file.alexalban.me/s/gAnPLMpcowyGmwL
PVE: https://file.alexalban.me/s/r33HPdcHLNcTkFB

The time is between 2022-06-05T22:00:02Z and 2022-06-05T22:02:10Z

Some VM IDs are: 1003, 6002 (I know they are different from the first message)
 
sadly that link to the pbs log is password protected so i can't look at it ;)
 
ok in the logs there is sadly not much more information... was the system under heavy load at that time?
these errors are a timeout when trying to flock the file responsible for tracking the active tasks (which should normally not be locked for long)...
 
dcsapak said:
ok in the logs there is sadly not much more information... was the system under heavy load at that time?
these errors are a timeout when trying to flock the file responsible for tracking the active tasks (which should normally not be locked for long)...
Click to expand...
Well, I'd say yes, I have many PVEs doing backups during the night. Before upgrading to 2.2 I have never had any issue with it...

Thanks
 
any special setup? where are your datastores ? which filesystem? any logs that might be relevant?
 
Not wanting to hijack this thread, but we are seeing failures since the upgrade too:

vzdump backup status (FQDN) : backup failed: could not activate storage 'FQDN': FQDN: error fetching datastores - 500 Can't connect to 192.168.5.100:8007

The network is up and fine, now outages, we are backing up every couple of hours but errors occur once or twice a day.

Edited to correct typo
 
DJI said:
Not wanting to hijack this thread, but we are seeing failures since the upgrade too:

vzdump backup status (FQDN) : backup failed: could not activate storage 'FQDN': FQDN: error fetching datastores - 500 Can't connect to 192.168.5.100:8007

The network is up and fine, now outages, we are backing up every couple of hours but errors occur once or twice a day.

Edited to correct typo
Click to expand...
Same here on some nodes.... also Network OK....
 
so, we're trying to reproduce the issue, but couldn't so far.
could you post the specs of the pbs? (cpu/memory/network/etc.) just so that we can get a picture what might be the issue
 
PBS

12 x AMD Ryzen 5 PRO 3600 6-Core Processor (1 Socket)
32GB RAM
OS Disks ZFS SSD 512GB
DATA Disks 4 x SATA 6TB ZFS

proxmox-backup: 2.2-1 (running kernel: 5.15.35-1-pve)
proxmox-backup-server: 2.2.3-2 (running version: 2.2.3)
pve-kernel-5.15: 7.2-4
pve-kernel-helper: 7.2-4
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-1-pve: 5.13.19-3
ifupdown2: 3.1.0-1+pmx3
libjs-extjs: 7.0.0-1
proxmox-backup-docs: 2.2.3-1
proxmox-backup-client: 2.2.3-1
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.5.1
pve-xtermjs: 4.16.0-1
smartmontools: 7.2-pve3
zfsutils-linux: 2.1.4-pve1

All remotes are:

proxmox-ve: 7.2-1 (running kernel: 5.15.35-3-pve)
pve-manager: 7.2-5 (running version: 7.2-5/12f1e639)
pve-kernel-5.15: 7.2-5
pve-kernel-helper: 7.2-5
pve-kernel-5.15.35-3-pve: 5.15.35-6
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-2
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-2
libpve-storage-perl: 7.2-5
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.3-1
proxmox-backup-file-restore: 2.2.3-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-2
pve-qemu-kvm: 6.2.0-10
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-3
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom