November 2017
Intermediate to advanced
494 pages
14h 29m
English
This occurs when a node falls out of quorum. To prevent an error occurring in the cluster configuration files, Proxmox puts the cluster filesystem in the read-only mode for the node in question. Run the following commands from the node with this issue. We have to stop the cluster service, start it in local mode, delete or move the existing corosync.conf file, and then restart the cluster. A new corosync.conf file will be synced with the node with a read-only issue. Perform the following steps to overcome this issue:
# systemctl stop pve-cluster