Hi,
I deinstalled the Cluster I made on my Proxmox 5.1 with first removing Node2 and than doing:
stop pve-cluster.service and corosync.service
then destroy /etc/corosync/* and /var/lib/pve-cluster
written here: https://forum.proxmox.com/threads/destroy-cluster-configuration.29092/
Now I can access the WebGUI, but my Server isn't listed there anymore... any ideas???
The error pvestadt status says: Failed to start PVE Status Daemon.
THe reason I deleted the cluster is that Node1 didn't shut down anymore..
I deinstalled the Cluster I made on my Proxmox 5.1 with first removing Node2 and than doing:
stop pve-cluster.service and corosync.service
then destroy /etc/corosync/* and /var/lib/pve-cluster
written here: https://forum.proxmox.com/threads/destroy-cluster-configuration.29092/
Now I can access the WebGUI, but my Server isn't listed there anymore... any ideas???
The error pvestadt status says: Failed to start PVE Status Daemon.
THe reason I deleted the cluster is that Node1 didn't shut down anymore..
Code:
systemctl start pvestatd.service
Job for pvestatd.service failed because the control process exited with error code.
See "systemctl status pvestatd.service" and "journalctl -xe" for details.
root@pve:~# systemctl status pvestatd.service
● pvestatd.service - PVE Status Daemon
Loaded: loaded (/lib/systemd/system/pvestatd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-02-10 23:48:26 CET; 2s ago
Process: 14253 ExecStart=/usr/bin/pvestatd start (code=exited, status=111)
CPU: 673ms
Feb 10 23:48:26 pve pvestatd[14253]: ipcc_send_rec[1] failed: Connection refused
Feb 10 23:48:26 pve pvestatd[14253]: ipcc_send_rec[2] failed: Connection refused
Feb 10 23:48:26 pve pvestatd[14253]: ipcc_send_rec[2] failed: Connection refused
Feb 10 23:48:26 pve pvestatd[14253]: ipcc_send_rec[3] failed: Connection refused
Feb 10 23:48:26 pve pvestatd[14253]: ipcc_send_rec[3] failed: Connection refused
Feb 10 23:48:26 pve pvestatd[14253]: Unable to load access control list: Connection refused
Feb 10 23:48:26 pve systemd[1]: pvestatd.service: Control process exited, code=exited status=111
Feb 10 23:48:26 pve systemd[1]: Failed to start PVE Status Daemon.
Feb 10 23:48:26 pve systemd[1]: pvestatd.service: Unit entered failed state.
Feb 10 23:48:26 pve systemd[1]: pvestatd.service: Failed with result 'exit-code'.
root@pve:~# systemctl status pvedaemon.service
● pvedaemon.service - PVE API Daemon
Loaded: loaded (/lib/systemd/system/pvedaemon.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2018-02-10 23:41:02 CET; 7min ago
Process: 7530 ExecStart=/usr/bin/pvedaemon start (code=exited, status=0/SUCCESS)
Main PID: 7772 (pvedaemon)
Tasks: 4 (limit: 4915)
Memory: 104.8M
CPU: 1.386s
CGroup: /system.slice/pvedaemon.service
├─7772 pvedaemon
├─7777 pvedaemon worker
├─7778 pvedaemon worker
└─7780 pvedaemon worker
Feb 10 23:41:00 pve systemd[1]: Starting PVE API Daemon...
Feb 10 23:41:02 pve pvedaemon[7772]: starting server
Feb 10 23:41:02 pve pvedaemon[7772]: starting 3 worker(s)
Feb 10 23:41:02 pve pvedaemon[7772]: worker 7777 started
Feb 10 23:41:02 pve pvedaemon[7772]: worker 7778 started
Feb 10 23:41:02 pve pvedaemon[7772]: worker 7780 started
Feb 10 23:41:02 pve systemd[1]: Started PVE API Daemon.