journalctl -b > $(hostname)-journal.txt and attach it here. Is this node part of a cluster or a standalone node?systemctl reset-failed pve-cluster.service you can reset the failed counter for the service, which should allow you to restart it via systemctl restart pve-cluster.service
The errors you show are expected if the pmxcfs is not mounted correctly at /etc/pve. These are just consequences, not the root cause.
pmxcfs is provided by the package pve-cluster. You should not copy around executables ecc. from other hosts, but rather reinstall the packages if the files provided by them might have been corrupted. Please verify the package file integrity via
dpkg -V pve-cluster and/or reinstallapt install --reinstall pve-cluster.Unable to get local IP address error indicates that the hostname is not resolved to the IP address, so something is off. What is the output of hostname --ip-address? What exactly did you change on the host?
systemctl stop pve-cluster
systemctl stop corosync
# Make sure both services are stopped via
systemctl status pve-cluster corosync
# Make sure you have no pmxcfs processes running that you started manually
killall pmxcfs
# Check the /etc/pve mountpoint is empty, if not you must move the files there to a different location
ls -l /etc/pve
# Start pmxcfs in local mode
pmxcfs -l
# Remove possibly lingering corosync config
rm /etc/pve/corosync.conf
rm -r /etc/corosync/*
# Stop pmxcfs again and finally start pve-cluster service
killall pmxcfs
systemctl start pve-clusterYou did not follow the commands and comments I posted, as you can see from the output, the pmxcfs is not mounted because the mountpoint is not empty.
