Hi all,
A recent update to CentOS 5.9 has broken my cluster's ability to fence
nodes. I have two Dell's which are both fenced via their DRAC6 cards. The
current configuration in cluster.conf for the fencing devices is:
fencedevice agent=fence_drac5 cmd_prompt=admin1-gt;
ipaddr=192.168.251.11
I have two Dell's which are both fenced via their DRAC6 cards.
Without your cluster config, we can only guess. Fencing w/ two nodes
requires specific startup config for this scenario. Given that, I presume you
can find your issue, or post your conf.
jlc
Thanks for the response. I just discovered the problem about 30' ago.
post_join_delay was set to the default of 3, meaning that it was only
waiting 3 seconds for the node to join before fencing it. Silly. After
changing that to 300 seconds, it worked fine.
The config was this way with 5.8 and
Turns out I spoke too soon.
Increasing the post_join_delay did at least allow me to restart the
cman+clvmd+gfs2+rgmanager services on each node, but if I reboot a node, it
will not rejoin the cluster.
If I start with both machines up, and cman stopped, I can start cman on
one, then then the
Turns out I spoke too soon.
Slow down cowboy, man fenced:)
See clean_start for example. There are more than one param needed
for a two node cluster.
https://fedorahosted.org/cluster/wiki/FAQ/Fencing#fence_stuck
https://fedorahosted.org/cluster/wiki/FAQ/Fencing#fence_startup
Much
Brilliant. Many thanks. I love great documentation: once the guns are
out, someone *must* win
Adam Wead
Systems and Digital Collections Librarian
Rock and Roll Hall of Fame and Museum
216.515.1960 (t)
215.515.1964 (f)
On Tue, Mar 5, 2013 at 8:44 PM,
6 matches
Mail list logo
