Hi @killmasta93 can you try to make backup file pvestatd.pid.lock and try to restart the pvestatd?
`mv /var/run/pvestatd.pid.lock /var/run/pvestatd.pid.lock.bak`
then
➜ ~ pvestatd restart
➜ ~ pvestatd status
but first kill the process id of pvestatd
Hallo,
Ich glaube das Problem von dein hosts file.
Versuchst du /etc/hosts zu bearbeiten
nach
127.0.0.1 localhost.localdomain localhost pvelocalhost
192.168.178.69 ProxServer.example.com debian-server
Dann mach hostname -f und apt install proxmox-ve
did you restart the server after editing /etc/network/interfaces and /etc/hosts?
could u post output of this commands:
ss -4 -a | grep 8006
curl -s -k https://127.0.0.1:8006 | grep title && echo "\n" && ss -4 -a | grep 8006
ip a
ip link
cat /etc/network/interfaces
cat /etc/hosts
Did you a OPNSense already installed? if yes try to disable CD/DVD go to Datacenter -> NodeName -> VMID -> Hardware -> CD/DVD click edit and select Do not use any media then ok
like this image :)
- What is version of your PVE? pveversion -v
- See which processes eat the SWAP with top or htop
- Check the journal of the PVE node for potential issues