Proxmox crash with message "pveproxy[2503]: worker 6682 started"

euler001

New Member
Jan 21, 2020
16
0
1
54
Hi,

Our Proxmox system crashed yesterday. After that, no one could log into it until I manually restart the proxmox server on site. I looked into the syslog and found out the crash started on Mar 19 08:58:21 with the message "pveproxy[2503]: worker 6682 started". I am using proxmox-ve: 5.4-1. I have no clue how this happened and how to prevent this from happening in the future. below are some relevant commands' prints out.

please help,

thanks,

Euler


Mar 19 08:56:00 fvcqaN systemd[1]: Starting Proxmox VE replication runner...
Mar 19 08:56:01 fvcqaN systemd[1]: Started Proxmox VE replication runner.
Mar 19 08:57:00 fvcqaN systemd[1]: Starting Proxmox VE replication runner...
Mar 19 08:57:01 fvcqaN systemd[1]: Started Proxmox VE replication runner.
Mar 19 08:58:00 fvcqaN systemd[1]: Starting Proxmox VE replication runner...
Mar 19 08:58:01 fvcqaN systemd[1]: Started Proxmox VE replication runner.
Mar 19 08:58:21 fvcqaN pveproxy[2101]: worker exit
Mar 19 08:58:21 fvcqaN pveproxy[2503]: worker 2101 finished
Mar 19 08:58:21 fvcqaN pveproxy[2503]: starting 1 worker(s)
Mar 19 08:58:21 fvcqaN pveproxy[2503]: worker 6682 started
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

root@fvcqaN:/etc# pveversion --verbose
proxmox-ve: 5.4-1 (running kernel: 4.15.18-12-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-35
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-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-50
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-25
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-19
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
 
thanks for your advice. I actually was in 6.1 before. 6.1 always crashed on my system. So I downgraded to 5.4. Then it seldom crashes. Thus, I do not think the upgrade is a viable solution.
 
Thus, I do not think the upgrade is a viable solution.
PVE 5.x has been EOL for a while so it's not supported anymore.

if you upgrade to the latest 6.x and you still get crashes then we can take a closer look at it