Proxmox PVE reboots automatically

[definedge]

Hello,

Our PROXMOX PVE reboots automatically.

Here is the error log at the time to reboot in pve logs:

pvestatd[2058]: VM 143 qmp command failed - VM 143 qmp command 'query-proxmox-support' failed - got timeout

We recently updated promox from 5.13.19-6-pve to 5.15.131-2-pve but still problem persists.

Any idea how to fix the issue?

Thanks

 

[Chris]

Hi,
are there any other errors in the logs around the time the Proxmox VE host reboots? You can get a paginated view of the systemd journal from around that time via journalctl --since <DATETIME> --until <DATETIME>.

Also, make sure to have the latest firmware and microcode updates for your system installed, see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_firmware_updates

 

[definedge]

Here are the logs : Systems doesn't logs few minutes before crash/reboot Jan 19 12:56:25 to Jan 19 13:12:02 (crash)

Jan 19 12:30:35 pve1 kernel: [28913.123392] device tap109i0 entered promiscuous mode
Jan 19 12:30:35 pve1 systemd-udevd[91178]: Using default interface naming scheme 'v247'.
Jan 19 12:30:35 pve1 systemd-udevd[91178]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 19 12:30:36 pve1 systemd-udevd[91178]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 19 12:30:36 pve1 kernel: [28913.176286] vmbr0: port 55(fwpr109p0) entered blocking state
Jan 19 12:30:36 pve1 kernel: [28913.176292] vmbr0: port 55(fwpr109p0) entered disabled state
Jan 19 12:30:36 pve1 kernel: [28913.176428] device fwpr109p0 entered promiscuous mode
Jan 19 12:30:36 pve1 kernel: [28913.176523] vmbr0: port 55(fwpr109p0) entered blocking state
Jan 19 12:30:36 pve1 kernel: [28913.176526] vmbr0: port 55(fwpr109p0) entered forwarding state
Jan 19 12:30:36 pve1 kernel: [28913.185126] fwbr109i0: port 1(fwln109i0) entered blocking state
Jan 19 12:30:36 pve1 kernel: [28913.185131] fwbr109i0: port 1(fwln109i0) entered disabled state
Jan 19 12:30:36 pve1 kernel: [28913.185267] device fwln109i0 entered promiscuous mode
Jan 19 12:30:36 pve1 kernel: [28913.185377] fwbr109i0: port 1(fwln109i0) entered blocking state
Jan 19 12:30:36 pve1 kernel: [28913.185379] fwbr109i0: port 1(fwln109i0) entered forwarding state
Jan 19 12:30:36 pve1 kernel: [28913.193879] fwbr109i0: port 2(tap109i0) entered blocking state
Jan 19 12:30:36 pve1 kernel: [28913.193884] fwbr109i0: port 2(tap109i0) entered disabled state
Jan 19 12:30:36 pve1 kernel: [28913.194078] fwbr109i0: port 2(tap109i0) entered blocking state
Jan 19 12:30:36 pve1 kernel: [28913.194080] fwbr109i0: port 2(tap109i0) entered forwarding state
Jan 19 12:30:36 pve1 systemd-udevd[91225]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jan 19 12:30:36 pve1 systemd-udevd[91225]: Using default interface naming scheme 'v247'.
Jan 19 12:30:37 pve1 pvedaemon[2080]: <root@pam> starting task UPIDve1:000164D8:002C1F11:65AA1E15:vncproxy:109:root@pam:
Jan 19 12:30:37 pve1 pvedaemon[91352]: starting vnc proxy UPIDve1:000164D8:002C1F11:65AA1E15:vncproxy:109:root@pam:
Jan 19 12:37:31 pve1 pveproxy[84182]: worker exit
Jan 19 12:37:32 pve1 pveproxy[2086]: worker 84182 finished
Jan 19 12:37:32 pve1 pveproxy[2086]: starting 1 worker(s)
Jan 19 12:37:32 pve1 pveproxy[2086]: worker 92493 started
Jan 19 12:43:33 pve1 pvedaemon[2080]: <root@pam> successful auth for user 'root@pam'
Jan 19 12:45:34 pve1 pveproxy[2086]: worker 83376 finished
Jan 19 12:45:34 pve1 pveproxy[2086]: starting 1 worker(s)
Jan 19 12:45:34 pve1 pveproxy[2086]: worker 93939 started
Jan 19 12:45:38 pve1 pveproxy[93938]: got inotify poll request in wrong process - disabling inotify
Jan 19 12:51:20 pve1 pvedaemon[2080]: <root@pam> starting task UPIDve1:00017361:002E0460:65AA22F0:vncproxy:119:root@pam:
Jan 19 12:51:20 pve1 pvedaemon[95073]: starting vnc proxy UPIDve1:00017361:002E0460:65AA22F0:vncproxy:119:root@pam:
Jan 19 12:52:33 pve1 pvedaemon[2079]: <root@pam> update VM 119: resize --disk scsi0 --size +80G
Jan 19 12:53:09 pve1 pvedaemon[2080]: <root@pam> end task UPIDve1:00017361:002E0460:65AA22F0:vncproxy:119:root@pam: OK
Jan 19 12:54:56 pve1 pveproxy[2086]: worker 87118 finished
Jan 19 12:54:56 pve1 pveproxy[2086]: starting 1 worker(s)
Jan 19 12:54:56 pve1 pveproxy[2086]: worker 95665 started
Jan 19 12:54:57 pve1 pveproxy[95662]: worker exit
Jan 19 12:55:15 pve1 pvedaemon[2078]: <root@pam> starting task UPIDve1:000175EA:002E6070:65AA23DB:vncproxy:119:root@pam:
Jan 19 12:55:15 pve1 pvedaemon[95722]: starting vnc proxy UPIDve1:000175EA:002E6070:65AA23DB:vncproxy:119:root@pam:
Jan 19 12:55:22 pve1 pvedaemon[2078]: <root@pam> end task UPIDve1:000175EA:002E6070:65AA23DB:vncproxy:119:root@pam: OK
Jan 19 12:55:22 pve1 pvedaemon[95750]: starting vnc proxy UPIDve1:00017606:002E6325:65AA23E2:vncproxy:109:root@pam:
Jan 19 12:55:22 pve1 pvedaemon[2078]: <root@pam> starting task UPIDve1:00017606:002E6325:65AA23E2:vncproxy:109:root@pam:
Jan 19 12:55:26 pve1 pvedaemon[2078]: <root@pam> end task UPIDve1:00017606:002E6325:65AA23E2:vncproxy:109:root@pam: OK
Jan 19 12:55:56 pve1 pvedaemon[2080]: <root@pam> update VM 109: -vmstatestorage ds1
Jan 19 12:56:20 pve1 pvestatd[2052]: VM 140 qmp command failed - VM 140 qmp command 'query-proxmox-support' failed - got timeout
Jan 19 12:56:25 pve1 pvestatd[2052]: VM 128 qmp command failed - VM 128 qmp command 'query-proxmox-support' failed - got timeout
Jan 19 13:12:02 pve1 systemd-modules-load[1325]: Inserted module 'iscsi_tcp'
Jan 19 13:12:02 pve1 kernel: [ 0.000000] Linux version 5.15.131-2-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PVE 5.15.131-3 (2023-12-01T13:42Z) ()

The firmware is not latest - we plan to upgrade.

Thanks

 

[mmatallana]

Hi there

I have the same problem , a VMs is in continues reboots without no reason , have any way out here t solve this?