Talk:Fencing
Revision as of 15:41, 11 April 2016 by Bernard S. (talk | contribs) (Complements for editing corosync.conf instead of cluster.conf, sort of draft for a separate page)
The process I use to edit corosync.conf (needs to be reviewed checked, tested and amended by a more knowledgeable person!!!)
1 - Edit /etc/corosync/corosync.conf
- of course make a backup first
- never forget increasing version number
2 - Check the content of /etc/pve/
- if /etc/pve/corosync.conf is writeable, simply copy /etc/corosync/corosync.conf to /etc/pve/corosync.conf, then restart the service corosync (note to editors... in fact, I have never done precisely that, since I was fighting to setup my cluster and I am not ready to take the risk to break it!!)
- if present but read-only... then your cluster is not OK, presumably because of a problem with corosync (and your other configuration details).
- stop corosync and switch to local-only mode:
- service corosync stop
- pmxcfs -l
- You should get the message that it works "even though corosync.conf is already present"
- If you get an error message "unable to get the lock"... check the presence of /var/lib/pve-cluster/.pmxcfs.lockfile and remove it, then re-issue pmxcfs -l
- You are now ready to update corosync.conf and re-launch the cluster
- cp /etc/corosync/corosync.conf /etc/pve/corosync.conf
- service corosync start
- service pve-cluster start
- if /etc/pve/ is empty (note to editors : not sure I remember correctly...)
- pmxcfs -l
- You should get the message that it works "even though corosync.conf is already present"
- If you get an error message "unable to get the lock"... check the presence of /var/lib/pve-cluster/.pmxcfs.lockfile and remove it, then re-issue pmxcfs -l
- You are now ready to update corosync.conf and re-launch the cluster
- cp /etc/corosync/corosync.conf /etc/pve/corosync.conf
- service corosync start
- service pve-cluster start
Remark: not sure if not needed to create /etc/pve/priv and /etc/pve/nodes if they are absent