try also disable the acpi if is it running , see following:
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Cluster_Administration/s1-acpi-CA.html
Regards,
Jorge Sanchez
On Thu, May 21, 2009 at 5:34 PM, ESGLinux <esggrupos@xxxxxxxxx> wrote:
2009/5/21 Jonathan Brassow <jbrassow@xxxxxxxxxx>On May 21, 2009, at 9:57 AM, ESGLinux wrote:
Hello,
these are the logs I get:
In node1:
May 21 11:33:44 NODE1 fenced[3840]: NODE2 not a cluster member after 5 sec post_fail_delay
May 21 11:33:44 NODE1 fenced[3840]: fencing node "NODE2"
May 21 11:33:44 NODE1 shutdown[5448]: shutting down for system halt
in node2:
May 21 11:33:45 NODE2 fenced[3843]: NODE1 not a cluster member after 5 sec post_fail_delay
May 21 11:33:45 NODE2 fenced[3843]: fencing node "NODE1"
May 21 11:33:45 NODE2 shutdown[5923]: shutting down for system halt
what I don´t know is way they lose the connection with the cluster, they are still connected (I only unplug a cable from the service network)
That may be something worth chasing down, as it appears that your cluster communication is on a network you don't expect?
How can I be sure about the network the nodes are using for communication? I think they do for the network I have configured to do that....
Also, are the nodes simply "shutting down", or are they being forcibly rebooted. If it is a casual shutdown, then it would appear that both nodes are trying to shutdown simultaneously.
they simply shutdown. They no reboot.
This is what I get every time I unplug the nework cable from eth0 of any of the two nodes. (they communicate through eth1...)
Greetings,
ESG
brassow
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
