Proxmox UI stops responding, Windows 2022 VM not responding, Linux VMs still have ping

[mopro]

Hi everyone,

I’ve been struggling with an issue where Proxmox VE (8.3) persistently reports "Guest Agent not running" for a Windows Server VM, even after multiple installation attempts.

Each time after installation and VM recovery on the fresh Proxmox, it works for almost two days and then the windows VM becomes inaccessible using ping and also the proxmox itself is not ping able. The linux machines on proxmox could be pinged. The proxmox UI also becomes inaccessible. I have setup proxmox with zfs. Previously, it was on ext4, but the disks where disappearing from vm and become inactive after similar amount of time. Each time the system goes into this mode, I should hard restart it and it comes back, works for another two days.

I appreciate any help on this issue.

Best

 

[fiona]

Hi,
please share the host system logs/journal from around the time of the issue as well as the output of pveversion -v. Upgrading to the current version is recommended in any case:
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#system_software_updates
https://pve.proxmox.com/wiki/Package_Repositories#_repositories_in_proxmox_ve

 

[mopro]

Thanks so much for your reply.
I just updated the proxmox and here are what you asked
root@proxmox:~# pveversion -v

proxmox-ve: 8.4.0 (running kernel: 6.8.12-10-pve)
pve-manager: 8.4.1 (running version: 8.4.1/2a5fa54a8503f96d)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.8.12-10-pve-signed: 6.8.12-10
proxmox-kernel-6.8: 6.8.12-10
proxmox-kernel-6.8.12-4-pve-signed: 6.8.12-4
ceph-fuse: 17.2.7-pve3
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.0
libpve-cluster-perl: 8.1.0
libpve-common-perl: 8.3.1
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.6
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.1-1
proxmox-backup-file-restore: 3.4.1-1
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.2
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.7
proxmox-widget-toolkit: 4.3.10
pve-cluster: 8.1.0
pve-container: 5.2.6
pve-docs: 8.4.0
pve-edk2-firmware: 4.2025.02-3
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.1
pve-firmware: 3.15-3
pve-ha-manager: 4.0.7
pve-i18n: 3.4.2
pve-qemu-kvm: 9.2.0-5
pve-xtermjs: 5.5.0-2
qemu-server: 8.3.12
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve2



And the latest event of the crash had the following log before it, which i do not see anything suspicions

May 04 16:27:09 proxmox kernel: fwln100i0: entered allmulticast mode
May 04 16:27:09 proxmox kernel: fwln100i0: entered promiscuous mode
May 04 16:27:09 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
May 04 16:27:09 proxmox kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
May 04 16:27:09 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
May 04 16:27:09 proxmox kernel: fwbr100i0: port 2(tap100i0) entered disabled state
May 04 16:27:09 proxmox kernel: tap100i0: entered allmulticast mode
May 04 16:27:09 proxmox kernel: fwbr100i0: port 2(tap100i0) entered blocking state
May 04 16:27:09 proxmox kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
May 04 16:27:09 proxmox pvedaemon[97494]: VM 100 started with PID 97504.
May 04 16:27:09 proxmox pvedaemon[2130]: <root@pam> end task UPIDroxmox:00017CD6:0018C6AE:6817793D:qmstart:100:root@pam: OK
May 04 16:27:18 proxmox pvedaemon[2128]: <root@pam> starting task UPIDroxmox:00017D89:0018CA2A:68177946:vncproxy:100:root@pam:
May 04 16:27:18 proxmox pvedaemon[97673]: starting vnc proxy UPIDroxmox:00017D89:0018CA2A:68177946:vncproxy:100:root@pam:
May 04 16:32:39 proxmox pveproxy[38594]: worker 86476 finished
May 04 16:32:39 proxmox pveproxy[38594]: starting 1 worker(s)
May 04 16:32:39 proxmox pveproxy[38594]: worker 99555 started
May 04 16:32:41 proxmox pveproxy[99554]: got inotify poll request in wrong process - disabling inotify
May 04 16:32:45 proxmox pveproxy[85524]: worker exit
May 04 16:32:45 proxmox pveproxy[38594]: worker 85524 finished
May 04 16:32:45 proxmox pveproxy[38594]: starting 1 worker(s)
May 04 16:32:45 proxmox pveproxy[38594]: worker 99599 started
May 04 16:33:54 proxmox pvedaemon[2128]: worker exit
May 04 16:33:54 proxmox pvedaemon[2127]: worker 2128 finished
May 04 16:33:54 proxmox pvedaemon[2127]: starting 1 worker(s)
May 04 16:33:54 proxmox pvedaemon[2127]: worker 100050 started
May 04 16:34:18 proxmox pvedaemon[2129]: <root@pam> successful auth for user 'root@pam'
May 04 16:34:33 proxmox pvedaemon[2129]: worker exit
May 04 16:34:33 proxmox pvedaemon[2127]: worker 2129 finished
May 04 16:34:33 proxmox pvedaemon[2127]: starting 1 worker(s)
May 04 16:34:33 proxmox pvedaemon[2127]: worker 100252 started
May 04 16:37:07 proxmox pvedaemon[2130]: worker exit
May 04 16:37:07 proxmox pvedaemon[2127]: worker 2130 finished
May 04 16:37:07 proxmox pvedaemon[2127]: starting 1 worker(s)
May 04 16:37:07 proxmox pvedaemon[2127]: worker 101169 started
May 04 16:41:46 proxmox pvedaemon[100050]: <root@pam> successful auth for user 'root@pam'
May 04 16:41:59 proxmox pveproxy[102870]: got inotify poll request in wrong process - disabling inotify
May 04 16:41:59 proxmox pveproxy[38594]: worker 90385 finished
May 04 16:41:59 proxmox pveproxy[38594]: starting 1 worker(s)
May 04 16:41:59 proxmox pveproxy[38594]: worker 102871 started
May 04 16:47:59 proxmox pvedaemon[100050]: <root@pam> starting task UPIDroxmox:00019A00:001AAF3D:68177E1F:vncproxy:100:root@pam:
May 04 16:47:59 proxmox pvedaemon[104960]: starting vnc proxy UPIDroxmox:00019A00:001AAF3D:68177E1F:vncproxy:100:root@pam:
May 04 16:48:00 proxmox pveproxy[99554]: worker exit
May 04 16:50:18 proxmox pvedaemon[100050]: <root@pam> successful auth for user 'root@pam'
May 04 16:51:47 proxmox pveproxy[99555]: worker exit
May 04 16:51:47 proxmox pveproxy[38594]: worker 99555 finished
May 04 16:51:47 proxmox pveproxy[38594]: starting 1 worker(s)
May 04 16:51:47 proxmox pveproxy[38594]: worker 106247 started
May 04 16:56:47 proxmox pvedaemon[100050]: <root@pam> successful auth for user 'root@pam'
May 04 17:01:16 proxmox pveproxy[38594]: worker 99599 finished
May 04 17:01:16 proxmox pveproxy[38594]: starting 1 worker(s)
May 04 17:01:16 proxmox pveproxy[38594]: worker 109554 started
May 04 17:01:20 proxmox pveproxy[109553]: got inotify poll request in wrong process - disabling inotify
May 04 17:02:46 proxmox systemd[1]: session-199.scope: Deactivated successfully.
May 04 17:02:46 proxmox systemd-logind[1716]: Session 199 logged out. Waiting for processes to exit.
May 04 17:02:46 proxmox systemd-logind[1716]: Removed session 199.
May 04 17:02:46 proxmox pveproxy[90384]: worker exit
May 04 17:03:00 proxmox pvedaemon[100050]: <root@pam> end task UPIDroxmox:00019A00:001AAF3D:68177E1F:vncproxy:100:root@pam: OK
May 04 17:03:01 proxmox pvedaemon[110133]: starting vnc proxy UPIDroxmox:0001AE35:001C0F42:681781A5:vncproxy:100:root@pam:
May 04 17:03:01 proxmox pvedaemon[100050]: <root@pam> starting task UPIDroxmox:0001AE35:001C0F42:681781A5:vncproxy:100:root@pam:
May 04 17:03:01 proxmox pveproxy[109553]: worker exit
May 04 17:05:19 proxmox pvedaemon[100252]: <root@pam> successful auth for user 'root@pam'
May 04 17:06:37 proxmox systemd[1]: session-202.scope: Deactivated successfully.
May 04 17:06:37 proxmox systemd-logind[1716]: Session 202 logged out. Waiting for processes to exit.
May 04 17:06:37 proxmox systemd-logind[1716]: Removed session 202.
May 04 17:06:37 proxmox pveproxy[102870]: worker exit
May 04 17:06:45 proxmox pvedaemon[100050]: <root@pam> starting task UPIDroxmox:0001B377:001C66EF:68178285:vncproxy:104:root@pam:
May 04 17:06:45 proxmox pvedaemon[111479]: starting vnc proxy UPIDroxmox:0001B377:001C66EF:68178285:vncproxy:104:root@pam:
May 04 17:08:39 proxmox pveproxy[38594]: worker 102871 finished
May 04 17:08:39 proxmox pveproxy[38594]: starting 1 worker(s)
May 04 17:08:39 proxmox pveproxy[38594]: worker 112164 started
May 04 17:08:39 proxmox pveproxy[112163]: got inotify poll request in wrong process - disabling inotify
May 04 17:11:52 proxmox pvedaemon[100252]: <root@pam> successful auth for user 'root@pam'
May 04 17:13:07 proxmox pveproxy[38594]: worker 106247 finished
May 04 17:13:07 proxmox pveproxy[38594]: starting 1 worker(s)
May 04 17:13:07 proxmox pveproxy[38594]: worker 113747 started
May 04 17:13:08 proxmox pveproxy[113746]: worker exit
May 04 17:17:01 proxmox CRON[115109]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
May 04 17:17:01 proxmox CRON[115110]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 04 17:17:01 proxmox CRON[115109]: pam_unix(cron:session): session closed for user root
May 04 17:17:47 proxmox pveproxy[112163]: problem with client ::ffff:172.30.30.121; Connection reset by peer
May 04 17:17:47 proxmox pvedaemon[100050]: <root@pam> end task UPIDroxmox:0001AE35:001C0F42:681781A5:vncproxy:100:root@pam: OK
May 04 17:17:47 proxmox pveproxy[112163]: worker exit
May 04 17:21:18 proxmox pvedaemon[100252]: <root@pam> successful auth for user 'root@pam'
May 04 17:22:20 proxmox pvedaemon[100050]: <root@pam> end task UPIDroxmox:0001B377:001C66EF:68178285:vncproxy:104:root@pam: OK
May 04 17:22:26 proxmox pvedaemon[116965]: starting vnc proxy UPIDroxmox:0001C8E5:001DD65A:68178632:vncproxy:104:root@pam:
May 04 17:22:26 proxmox pvedaemon[100252]: <root@pam> starting task UPIDroxmox:0001C8E5:001DD65A:68178632:vncproxy:104:root@pam:
May 04 17:26:40 proxmox smartd[1708]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 138 to 141
May 04 17:26:40 proxmox smartd[1708]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 154 to 158
May 04 17:37:18 proxmox pvedaemon[100252]: <root@pam> successful auth for user 'root@pam'
May 04 17:37:28 proxmox pvedaemon[100252]: <root@pam> end task UPIDroxmox:0001C8E5:001DD65A:68178632:vncproxy:104:root@pam: OK
May 04 17:37:35 proxmox pvedaemon[122252]: starting vnc proxy UPIDroxmox:0001DD8C:001F3991:681789BF:vncproxy:104:root@pam:
May 04 17:37:35 proxmox pvedaemon[101169]: <root@pam> starting task UPIDroxmox:0001DD8C:001F3991:681789BF:vncproxy:104:root@pam:
May 04 17:38:54 proxmox pvedaemon[100050]: worker exit
May 04 17:38:54 proxmox pvedaemon[2127]: worker 100050 finished
May 04 17:38:54 proxmox pvedaemon[2127]: starting 1 worker(s)
May 04 17:38:54 proxmox pvedaemon[2127]: worker 122728 started
May 04 17:43:08 proxmox pveproxy[109554]: worker exit
May 04 17:43:08 proxmox pveproxy[38594]: worker 109554 finished
May 04 17:43:08 proxmox pveproxy[38594]: starting 1 worker(s)
May 04 17:43:08 proxmox pveproxy[38594]: worker 124224 started
May 04 17:50:13 proxmox pvedaemon[101169]: <root@pam> successful auth for user 'root@pam'
May 04 17:50:55 proxmox pvedaemon[101169]: worker exit
May 04 17:50:55 proxmox pvedaemon[2127]: worker 101169 finished
May 04 17:50:55 proxmox pvedaemon[2127]: starting 1 worker(s)
May 04 17:50:55 proxmox pvedaemon[2127]: worker 126995 started
May 04 17:52:40 proxmox pvedaemon[100252]: worker exit
May 04 17:52:40 proxmox pvedaemon[2127]: worker 100252 finished
May 04 17:52:40 proxmox pvedaemon[2127]: starting 1 worker(s)
May 04 17:52:40 proxmox pvedaemon[2127]: worker 127563 started
May 04 17:52:42 proxmox pvedaemon[127572]: starting vnc proxy UPIDroxmox:0001F254:00209BDC:68178D4A:vncproxy:104:root@pam:
May 04 17:52:42 proxmox pvedaemon[126995]: <root@pam> starting task UPIDroxmox:0001F254:00209BDC:68178D4A:vncproxy:104:root@pam:
May 04 17:53:18 proxmox pvedaemon[122728]: <root@pam> successful auth for user 'root@pam'
May 04 17:53:30 proxmox pveproxy[112164]: worker exit
May 04 17:53:30 proxmox pveproxy[38594]: worker 112164 finished
May 04 17:53:30 proxmox pveproxy[38594]: starting 1 worker(s)
May 04 17:53:30 proxmox pveproxy[38594]: worker 127849 started
May 04 17:55:39 proxmox pvedaemon[127563]: <root@pam> successful auth for user 'root@pam'
May 04 17:56:40 proxmox smartd[1708]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 141 to 144
May 04 17:56:40 proxmox smartd[1708]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 158 to 162
May 04 17:57:40 proxmox pveproxy[38594]: worker 113747 finished
May 04 17:57:40 proxmox pveproxy[38594]: starting 1 worker(s)
May 04 17:57:40 proxmox pveproxy[38594]: worker 129229 started
May 04 17:57:41 proxmox pveproxy[129228]: worker exit
May 04 18:01:27 proxmox kernel: perf: interrupt took too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
May 04 18:07:44 proxmox pvedaemon[126995]: <root@pam> end task UPIDroxmox:0001F254:00209BDC:68178D4A:vncproxy:104:root@pam: OK
May 04 18:07:51 proxmox pvedaemon[126995]: <root@pam> starting task UPIDroxmox:000205EE:0021FEDB:681790D7:vncproxy:104:root@pam:
May 04 18:07:51 proxmox pvedaemon[132590]: starting vnc proxy UPIDroxmox:000205EE:0021FEDB:681790D7:vncproxy:104:root@pam:
-- Reboot --


I really appreciate your help.