“killall pmxcfs”How to recover from mistakenly executing this command

Zhuy Chin

New Member
Jan 18, 2024
6
0
1
After executing this command, the connection to the virtual machine under the PVE server is normal. Then, restart the PVE server using the reboot command. At present, we are unable to connect to the virtual machine on the server and access the page on port 8006 of the PVE platform. How should I recover
1705546515360.png
1705546578995.png

1705546617165.png
 

Attachments

  • 1705546487593.png
    1705546487593.png
    49.3 KB · Views: 1
Last edited:
Hi,
please create a dump of the systemd journal since boot on node pve1 via journalctl -b > $(hostname)-journal.txt and attach it here. Is this node part of a cluster or a standalone node?

With 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
 
Thanks for your reply!
is a standalone node,
View attachment 61579
View attachment 61577
The errors you show are expected if the pmxcfs is not mounted correctly at /etc/pve. These are just consequences, not the root cause.

You will have to provide the requested output to see what exactly the problem is, but from your screenshots I got the suspicion you were trying to change the hostname and might have missed some configuration changes? Please follow the steps here if that is the case https://pve.proxmox.com/wiki/Renaming_a_PVE_node

Edit: Also make sure to not pollute you mountpoint by creating files/directories there while the pmxcfs is not mounted. Seems like you dumped the journal to exactly that location. This might impede the correct mounting!
 
Last edited:
pmxcfs the following prompt appeared:
1705567622149.png
Afterwards, I replaced the undamaged files from other PVE servers here,the following prompt appeared:
1705568061870.png
The host name has not been changed
1705568759393.png
pmxcfs,Can it be reinstalled separately?
 
pmxcfs the following prompt appeared:
View attachment 61581
Afterwards, I replaced the undamaged files from other PVE servers here,the following prompt appeared:
View attachment 61582
The host name has not been changed
View attachment 61588
pmxcfs,Can it be reinstalled separately?
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.

The 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?
 
1705574592146.png
Attempt to delete the cluster created in the PVE management page from the command line, no modifications were made to the IP.
Here are some commands that have been executed:
1705574406974.png
 
Last edited:
Okay, so this was a cluster. Try the following:
Code:
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-cluster

Also, your IP address configured on the network interface does not match the one configured in /etc/hosts. You will have to fix that as well, even better to do this before anything else, so that you should be able to download and reinstall the pve-cluster package, which does not seem possible at the moment.
 
Last edited:
Is this related to not being able to reinstall pve-cluster ?
View attachment 61602
You 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.
 
Last edited:

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!