trying to acquire cfs lock 'file-replication_cfg

H

HFernandez

Active Member
May 20, 2019
16
1
43
125
Hello everyone, this error happened to me several times and it is solved by restarting the node with the error, but I would like to solve it without restarting it:

syslog:
Oct 5 09:04:00 h6 systemd[1]: Starting Proxmox VE replication runner...
Oct 5 09:04:00 h6 pvesr[10680]: trying to acquire cfs lock 'file-replication_cfg' ...
Oct 5 09:04:01 h6 pvesr[10680]: trying to acquire cfs lock 'file-replication_cfg' ...
Oct 5 09:04:02 h6 pvesr[10680]: trying to acquire cfs lock 'file-replication_cfg' ...
Oct 5 09:04:03 h6 pvesr[10680]: trying to acquire cfs lock 'file-replication_cfg' ...
Oct 5 09:04:04 h6 pvesr[10680]: trying to acquire cfs lock 'file-replication_cfg' ...
Oct 5 09:04:05 h6 pvesr[10680]: trying to acquire cfs lock 'file-replication_cfg' ...
Oct 5 09:04:06 h6 pvesr[10680]: trying to acquire cfs lock 'file-replication_cfg' ...
Oct 5 09:04:07 h6 pvesr[10680]: trying to acquire cfs lock 'file-replication_cfg' ...
Oct 5 09:04:08 h6 pvesr[10680]: trying to acquire cfs lock 'file-replication_cfg' ...
Oct 5 09:04:09 h6 pvesr[10680]: error with cfs lock 'file-replication_cfg': no quorum!
Oct 5 09:04:09 h6 systemd[1]: pvesr.service: Main process exited, code=exited, status=13/n/a
Oct 5 09:04:09 h6 systemd[1]: Failed to start Proxmox VE replication runner.
Oct 5 09:04:09 h6 systemd[1]: pvesr.service: Unit entered failed state.
Oct 5 09:04:09 h6 systemd[1]: pvesr.service: Failed with result 'exit-code'.

It is a 3 node HA.
Virtual Environment 5.4-5

I have tried with:
systemctl stop pvesr
systemctl stop pvesr.timer
and has not fixed the error

Via web I can access the other nodes of the cluster but the node in question appears to me with a question mark (?) If I access the node via web the other nodes appear to me with the question mark
 
HFernandez said:
Oct 5 09:04:09 h6 pvesr[10680]: error with cfs lock 'file-replication_cfg': no quorum!
Click to expand...
Your node has fallen off the quorum, i.e. the cluster. As such it is inoperable.

Check your cluster networking, make sure the nodes can reach it other (ping, ssh), and see if there's anything in the logs about loosing quorum preceding the entries you posted.
 
Hi Stefan, the nodes are already visible, and the cluster is working, what I want is to remove the error but I would like to solve it without restarting the node.

It's possible?
 
If you are getting the error you posted, your nodes are certainly not in sync. Otherwise it would be working.

Check and post the output of pvecm status (on all nodes) please.
 
You must log in or register to reply here.
Top Bottom