Failure to shutdown, migrate, backup lxc

[buyiyo]

Hello,

I am having recurring problems on my production nodes with proxmox.

When scheduling backup jobs in snapshot mode, they sometimes hang and if I finish the job from GUI, the host node starts high IO / Delay.

This causes that it is not possible from that moment to carry out backups in other containers within the same node, as well as it does not allow to turn off lxc nor to carry out migrations.

Just rebooting the node makes it work again.

Is this a bug known to the Proxmox team?
Is there a solution, that does not happen by rebooting the node?

The environment on which the failure occurs on a recurring basis is with CEPH storage and the backups are hosted in NFS

Can anyone help me about it?

Thank you.

 

[matrix]

what is the version of PVE?
there is any error in syslog?

 

[buyiyo]

Hello,

Sorry for the delay in answering but I was on night maintenance.

This is the output of running pveversion -v on the affected node

proxmox-ve: 5.4-2 (running kernel: 4.15.18-27-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-16
pve-kernel-4.15.18-27-pve: 4.15.18-55
pve-kernel-4.15.18-26-pve: 4.15.18-54
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph: 12.2.13-pve1~bpo9
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-56
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-42
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-56
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

Attached a piece of log from the date the failure occurred

Thank you.

 

[matrix]

Proxmox 5 is already EOL, try to upgrade to Proxmox 6.2
https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0