pve-cluster not starting

V

vadavo

Renowned Member
Dec 20, 2015
16
0
66
35
Hello,

In one of our nodes, pve-cluster are with status "failed". The we try to start:

Job for pve-cluster.service failed. See 'systemctl status pve-cluster.service' and 'journalctl -xn' for details.
TASK ERROR: command 'systemctl start pve-cluster' failed: exit code 1

Using command systemctl status pve-cluster we can see:

Code: 
Dec 26 15:10:28 nd pmxcfs[20660]: [main] notice: unable to aquire pmxcfs lock - trying again

Dec 26 15:10:28 nd pmxcfs[20660]: [main] notice: unable to aquire pmxcfs lock - trying again

Dec 26 15:10:38 nd pmxcfs[20660]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable

Dec 26 15:10:38 nd pmxcfs[20660]: [main] notice: exit proxmox configuration filesystem (-1)

Dec 26 15:10:38 nd pmxcfs[20660]: [main] crit: unable to aquire pmxcfs lock: Resource temporarily unavailable

Dec 26 15:10:38 nd pmxcfs[20660]: [main] notice: exit proxmox configuration filesystem (-1)

Dec 26 15:10:38 nd systemd[1]: pve-cluster.service: control process exited, code=exited status=255
Dec 26 15:10:38 nd systemd[1]: Failed to start The Proxmox VE cluster filesystem.
Dec 26 15:10:38 nd systemd[1]: Unit pve-cluster.service entered failed state.


How Can we solved the problem?
 
Check that multicast works. There are threads with examples of some test outputs.
Post test results. Others may be able to help evaluate the tests.
 
Hello,

Unicast test:

Code: 
ping -f X.X.X.X.
PING X.X.X.X (X.X.X.X) 56(84) bytes of data.
.^C
--- X.X.X.X ping statistics ---
56253 packets transmitted, 56252 received, 0% packet loss, time 6827ms
rtt min/avg/max/mdev = 0.072/0.102/14.757/0.107 ms, ipg/ewma 0.121/0.106 ms

Multicast test:

Code: 
omping -c 10000 -i 0.001 -F -q X.X.X.X
omping: Can't find local address in arguments
 
You must log in or register to reply here.
Top Bottom