[SOLVED] Proxmox-WebGui and qm hang on the console

B

BrotherJ

Active Member
Sep 14, 2019
31
2
28
33
Hello everyone,

I'm a bit at a loss at the moment. First of all, I have installed Proxmox Virtual Environment 8.0.2. And so far logging into the WebGui on port 8006 has not been a problem. This suddenly no longer works and I can no longer display the Vms with
Code: 
qm list
on the console, the command hangs.

I tried restarting the service or starting it when it hung with this result:

Code: 
systemctl start pveproxy.service
Job for pveproxy.service failed because a timeout was exceeded.
See "systemctl status pveproxy.service" and "journalctl -xeu pveproxy.service" for details.
root@neckar1 ~ # systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
     Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; preset: enabled)
     Active: activating (start-pre) since Sun 2024-03-24 16:33:14 CET; 1min 28s ago
Cntrl PID: 3776420 (pvecm)
      Tasks: 10 (limit: 154393)
     Memory: 482.8M
        CPU: 221ms
     CGroup: /system.slice/pveproxy.service
             ├─1567631 /usr/bin/perl -T /usr/bin/pveproxy restart
             ├─2044960 "pveproxy worker"
             ├─2958233 "pveproxy worker"
             ├─2958444 "pveproxy worker"
             ├─3725479 /usr/bin/perl -T /usr/bin/pveproxy stop
             ├─3743593 /usr/bin/perl /usr/bin/pvecm updatecerts --silent
             ├─3753205 /usr/bin/perl /usr/bin/pvecm updatecerts --silent
             ├─3767598 /usr/bin/perl /usr/bin/pvecm updatecerts --silent
             ├─3776420 /usr/bin/perl /usr/bin/pvecm updatecerts --silent
             └─3776421 /usr/bin/perl /usr/bin/pvecm updatecerts --silent

Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 3725479 (pveproxy) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 3743593 (pvecm) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 3753205 (pvecm) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 3767598 (pvecm) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
root@neckar1 ~ # journalctl -xeu pveproxy.service
Journal file /var/log/journal/a2baf8418bcd40ecbe120fba98455f74/system@00061429cd0e4961-298067ed37ced1cd.journal~ is truncated, ignoring file.
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit pveproxy.service has finished with a failure.
░░
░░ The job identifier is 20169952 and the job result is failed.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 3.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit pveproxy.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Mar 24 16:33:14 neckar1 systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
░░ 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 20170696 and the job result is done.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 2044960 (pveproxy worker) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 2958233 (pveproxy worker) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 2958444 (pveproxy worker) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 1567631 (pveproxy) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 3725479 (pveproxy) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 3743593 (pvecm) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 3753205 (pvecm) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 systemd[1]: pveproxy.service: Found left-over process 3767598 (pvecm) in control group while starting unit. Ignoring.
Mar 24 16:33:14 neckar1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Mar 24 16:33:14 neckar1 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 20170696.
Mar 24 16:34:45 neckar1 systemd[1]: pveproxy.service: start-pre operation timed out. Terminating.

On port 8006 is the server listening:
Code: 
ss -tlnp | grep 8006
LISTEN 212    4096               *:8006             *:*    users:(("pveproxy worker",pid=2958444,fd=6),("pveproxy worker",pid=2958233,fd=6),("pveproxy worker",pid=2044960,fd=6))
Code: 
ss -tlnp | grep pveproxy
LISTEN 212    4096               *:8006             *:*    users:(("pveproxy worker",pid=2958444,fd=6),("pveproxy worker",pid=2958233,fd=6),("pveproxy worker",pid=2044960,fd=6))
On the other hand, the VMs appear to be running because mail, web and DNS servers are accessible from outside. How do I get the webgui working again and the qm command? I would like to avoid a complete reboot of the Proxmox server because the mail server is particularly essential.

Best regards

BrotherJ
 
You must log in or register to reply here.
Top Bottom