Hi,
Please can I get some help. As the title implies, I have a proxmox node that goes offline, but the containers and VMs are still running fine.
I can ssh to the proxmox node but I'm not sure what to check.
The only thing I have checked is the disk space and that is fine also.
I also tried
i tried
does anyone have any ideas?
Please can I get some help. As the title implies, I have a proxmox node that goes offline, but the containers and VMs are still running fine.
I can ssh to the proxmox node but I'm not sure what to check.
The only thing I have checked is the disk space and that is fine also.
I also tried
systemctl restart pveproxy
but that seems like it hangs for quite a while and then it displays this:
Code:
Job for pveproxy.service failed because a timeout was exceeded.
See "systemctl status pveproxy.service" and "journalctl -xeu pveproxy.service" for details.
i tried
journalctl -xeu pveproxy.service
and it shows me this:
Code:
░░ Subject: A stop job for unit pveproxy.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit pveproxy.service has finished.
░░
░░ The job identifier is 2397 and the job result is done.
Oct 03 08:38:30 SonyProx systemd[1]: pveproxy.service: Found left-over process 1714 (pveproxy) in control group while starting unit. Ignoring.
Oct 03 08:38:30 SonyProx systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 03 08:38:30 SonyProx systemd[1]: pveproxy.service: Found left-over process 69124 (pveproxy worker) in control group while starting unit. Ignoring.
Oct 03 08:38:30 SonyProx systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 03 08:38:30 SonyProx systemd[1]: pveproxy.service: Found left-over process 74664 (pveproxy worker) in control group while starting unit. Ignoring.
Oct 03 08:38:30 SonyProx systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 03 08:38:30 SonyProx systemd[1]: pveproxy.service: Found left-over process 77089 (pveproxy worker) in control group while starting unit. Ignoring.
Oct 03 08:38:30 SonyProx systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 03 08:38:30 SonyProx systemd[1]: pveproxy.service: Found left-over process 81379 (pveproxy) in control group while starting unit. Ignoring.
Oct 03 08:38:30 SonyProx systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 03 08:38:30 SonyProx systemd[1]: pveproxy.service: Found left-over process 139724 (pveproxy) in control group while starting unit. Ignoring.
Oct 03 08:38:30 SonyProx systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 03 08:38:30 SonyProx systemd[1]: pveproxy.service: Found left-over process 140609 (pvecm) in control group while starting unit. Ignoring.
Oct 03 08:38:30 SonyProx systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 03 08:38:30 SonyProx systemd[1]: pveproxy.service: Found left-over process 141551 (pvecm) in control group while starting unit. Ignoring.
Oct 03 08:38:30 SonyProx systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 03 08:38:30 SonyProx systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
░░ Subject: A start job for unit pveproxy.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has begun execution.
░░
░░ The job identifier is 2397.
Oct 03 08:40:00 SonyProx systemd[1]: pveproxy.service: start-pre operation timed out. Terminating.
Oct 03 08:41:30 SonyProx systemd[1]: pveproxy.service: State 'stop-sigterm' timed out. Killing.
Oct 03 08:41:30 SonyProx systemd[1]: pveproxy.service: Killing process 142437 (pvecm) with signal SIGKILL.
Oct 03 08:41:30 SonyProx systemd[1]: pveproxy.service: Killing process 1714 (pveproxy) with signal SIGKILL.
Oct 03 08:41:30 SonyProx systemd[1]: pveproxy.service: Killing process 69124 (pveproxy worker) with signal SIGKILL.
Oct 03 08:41:30 SonyProx systemd[1]: pveproxy.service: Killing process 74664 (pveproxy worker) with signal SIGKILL.
Oct 03 08:41:30 SonyProx systemd[1]: pveproxy.service: Killing process 77089 (pveproxy worker) with signal SIGKILL.
Oct 03 08:41:30 SonyProx systemd[1]: pveproxy.service: Killing process 81379 (pveproxy) with signal SIGKILL.
Oct 03 08:41:30 SonyProx systemd[1]: pveproxy.service: Killing process 139724 (pveproxy) with signal SIGKILL.
Oct 03 08:41:30 SonyProx systemd[1]: pveproxy.service: Killing process 140609 (pvecm) with signal SIGKILL.
Oct 03 08:41:30 SonyProx systemd[1]: pveproxy.service: Killing process 141551 (pvecm) with signal SIGKILL.
Oct 03 08:43:00 SonyProx systemd[1]: pveproxy.service: Processes still around after SIGKILL. Ignoring.
does anyone have any ideas?