On Thu, 07/05/2012 06:25 PM, Errol Neal <en...@businessgrade.com> wrote:
> Hi again. I was hoping to get some insight into why two nodes get rebooted in 
> my cluster when I halt one of of them. 
> 
> I'm running corosync 1.1.4 and pacemaker-1.1.6 on CentOS 6.2. I've put my 
> configuration up on pastebin if anyone would like to take a look
> 
> http://pastebin.com/raw.php?i=6cAkJ3Qk
> 
> Could this be related?
> 

Hi again. Any thoughts about this issue? Could it be a bug in the xenapi 
fencing agent? I even tried upgrading pacemaker to 1.1.8 and I'm still loosing 
two nodes when I bring down one. For example, I'll bring down nas1-dev3 by 
turning off it's nic. I expect it to get fenced. But then a few seconds latter, 
a good node will also get fenced. What I'm then left with is one node and a 
semi-working service. 

Thanks again for any insight you can give..

_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to