Problem looks at Failover domain's nodes priority. Same nodes has adjusted by different priority. it's would be triggerig unexpected fences. Maybe you can solve while step by step active your FO domains. (Ofcourse after all newtork and firewall settings right and w/o problem) Senol Erdogan <div class="gmail_quote">On Jun 4, 2014 11:06 AM, "Schaefer, Micah" <<a href="mailto:Micah.Schaefer@jhuapl.edu">Micah.Schaefer@jhuapl.edu</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I have a 4 node cluster, running a single service group. I have been seeing node1 fence node3 while node3 is actively running the service group at random intervals. Rgmanager logs show no failures in service checks, and no other logs provide any useful information. How can I go about finding out why node1 is fencing node3? I currently set up the failover domain to be restricted and not include node3. cluster.conf : <a href="http://pastebin.com/xYy6xp6N" target="_blank">http://pastebin.com/xYy6xp6N</a> -- Linux-cluster mailing list <a href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/linux-cluster" target="_blank">https://www.redhat.com/mailman/listinfo/linux-cluster</a> </blockquote></div>