WebUI down. Check services?

RockNLol

Member
Sep 13, 2020
45
2
13
hi,
I'm new to proxmox and am just fooling around a bit with it before I want to deploy it to my home setup.
In my test setup I just removed a node out of a cluster and rebooted it. Now I can't access the WebUI of said node.
How can I list proxmox services and if they are running? Is journalctl -xe the only "logfile"?

It seems pveproxy is not starting. All I get from systemctl pveproxy status is:
Code:
root@proxmoxle:~# systemctl status pveproxy.service
● pveproxy.service - PVE API Proxy Server
   Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-09-13 13:24:41 CEST; 4s ago
  Process: 2779 ExecStartPre=/usr/bin/pvecm updatecerts --silent (code=exited, status=0/SUCCESS)
  Process: 2781 ExecStart=/usr/bin/pveproxy start (code=exited, status=255/EXCEPTION)

Sep 13 13:24:41 proxmoxle systemd[1]: pveproxy.service: Service RestartSec=100ms expired, scheduling restart.
Sep 13 13:24:41 proxmoxle systemd[1]: pveproxy.service: Scheduled restart job, restart counter is at 5.
Sep 13 13:24:41 proxmoxle systemd[1]: Stopped PVE API Proxy Server.
Sep 13 13:24:41 proxmoxle systemd[1]: pveproxy.service: Start request repeated too quickly.
Sep 13 13:24:41 proxmoxle systemd[1]: pveproxy.service: Failed with result 'exit-code'.
Sep 13 13:24:41 proxmoxle systemd[1]: Failed to start PVE API Proxy Server.

journalctl -xe gives me:
Code:
Sep 13 13:24:41 proxmoxle systemd[1]: pvedaemon.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pvedaemon.service has entered the 'failed' state with result 'exit-code'.
Sep 13 13:24:41 proxmoxle systemd[1]: Failed to start PVE API Daemon.
-- Subject: A start job for unit pvedaemon.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit pvedaemon.service has finished with a failure.
--
-- The job identifier is 3064 and the job result is failed.
Sep 13 13:24:41 proxmoxle systemd[1]: pveproxy.service: Start request repeated too quickly.
Sep 13 13:24:41 proxmoxle systemd[1]: pveproxy.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit pveproxy.service has entered the 'failed' state with result 'exit-code'.
Sep 13 13:24:41 proxmoxle systemd[1]: Failed to start PVE API Proxy Server.
-- Subject: A start job for unit pveproxy.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support

this is not really giving me answers as to why they are failing to start. Or am I overlooking something?

best regards,
RockNLol
 
I think your /etc/pve drive doesn't work because pvecm isn't working.

If you'r sure what you doing try to convert that node to single mode: "pvecm expected 1" but you need to be 100% sure you'r not making any conflicts and that node is realy removed (I would disconnect it from LAN).
 
Since this is just a test setup I moved the VMs over to another drive, formatted the system drive and started from scratch. I'll avoid clusters when I roll out proxmox to my home servers.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!