The fence_na.log seems very similar to the issue in this thread: http://forum.proxmox.com/archive/index.php/t-8637.html
fbc240 s009 ~ # fence_tool ls
fence domain
member count 4
victim count 0
victim now 0
master nodeid 1
wait state none
members 1 3 4 5
fbc240 s009 ~ # grep fencing /var/log/syslog
fbc240 s009 ~ #
fbc240 s009 ~ # fence_tool ls
fence domain
member count 4
victim count 0
victim now 0
master nodeid 1
wait state none
members 1 3 4 5
fbc240 s009 ~ # grep fencing /var/log/syslog
fbc240 s009 ~ #
In case there is not a software update for rgmanager coming soon, do you have a suggestion to fix this problem?
I will try to upload an update to pvetest next week.
this morning I tried turning off all nodes, then starting one at a time.
And you set expexted votes after each node start (else you do not have quorum and rgmanager will not start)?
And you set expexted votes after each node start (else you do not have quorum and rgmanager will not start)?
<cman expected_votes="2"/>
I added
expected_votes="2"
to cluster.conf and activated.
when there will be a patch for debian ?
I refer to this dialogue
"06-16-2012
I will try to upload an update to pvetest next week. Best
Has bug 105 been tested to confirm the issue is fixed?That is already uploaded to stable.