Web interface and service stopped working

Dec 29, 2020
7
0
6
39
Hey all,

I have the latest VE installed but I recently had the Web interface just stop working. I can't restart any of the services either. My hostname is correct, I can ssh to the server without a problem but I keep getting the following errors.

server error.png

I've tried running a reinstall, and I've tried re-issuing the certs as per the link below

https://pve.proxmox.com/wiki/Proxmox_SSL_Error_Fixing

Nothing is working. Please help

Thanks
 
are there any other messages in the syslog/journal? is there a key/cert in /etc/pve/local ?
 
It seems that our configuration filesystem could not start, it's normally mounted at /etc/pve.
Can you please check the for the first (top-most) errors on the following command and post the output here:
Bash:
journalctl -b -u pve-cluster
 
Thought so, you created those cert/key files inside /etc/pve while pmxcfs was not mounted, so it cannot be mounted now as the directory is not empty.

Let's try the following:

Bash:
systemctl reset-failed pve-cluster
mv /etc/pve /etc/pve.old
systemctl restart pve-cluster

Note, there's a chance that there's another error, as the initial problem may not have been the non-empty directory.
If so, please post the same journalctl output again.
 
Thought so, you created those cert/key files inside /etc/pve while pmxcfs was not mounted, so it cannot be mounted now as the directory is not empty.

Let's try the following:

Bash:
systemctl reset-failed pve-cluster
mv /etc/pve /etc/pve.old
systemctl restart pve-cluster

Note, there's a chance that there's another error, as the initial problem may not have been the non-empty directory.
If so, please post the same journalctl output again.
Thanks that part seemed to work, but now how do I get my VM back?

1615355352347.png
 
I saw similar issue on my server. It was caused by the hostname change with the hostnamectl. The response of the command hostname -i began answering with an empty response. Set it up to result with a real IP and restart a proxmox instance. That should fix the issue.