Server Reboot during large pve-zsync backup

[yena]

Hello,
I'm experiencing a lot of reboot at first pve-rsync backup.
( this is the therd different server )
I't happen on large KVM VPS ( > 100G ).

I have checked syslog and i see:
Dec 14 16:23:22 ecom7dic pve-ha-lrm[2408]: loop take too long (71 seconds)

pveversion -V
proxmox-ve: 4.4-76 (running kernel: 4.4.15-1-pve)
pve-manager: 4.4-1 (running version: 4.4-1/eb2d6f1e)
pve-kernel-4.4.35-1-pve: 4.4.35-76
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.15-1-pve: 4.4.15-60
pve-kernel-4.2.8-1-pve: 4.2.8-41
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.2.3-2-pve: 4.2.3-22
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-101
pve-firmware: 1.1-10
libpve-common-perl: 4.0-83
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-70
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-1
pve-qemu-kvm: 2.7.0-9
pve-container: 1.0-88
pve-firewall: 2.0-33
pve-ha-manager: 1.0-38
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.6-2
lxcfs: 2.0.5-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve8

Someone have the same problem ?
Thanks

 

[LnxBil]

What ZFS version? Update outdated kernel (or reboot if already updated).

Please configure crashkernel to get "real" information about the crash.

 

[fabian]

you seem to have an incomepletely upgraded node, please make sure it is updated using "apt-get update; apt-get dist-upgrade" and reboot.