[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Linux-cluster] Problem with fenced on cluster with 2 BladeCenter machines: 1st machine is remove physically. The remaining one does not became Active (waiting for fenced)


I have a Cluster Redhat made with 2 nodes IBM blades on Blade Center chassis.
(fenced version 1.32.6)

I have done the following test:
I have removed physically the node 1 machine (the Active one).
The second one is never became active one. "Clustat" command does not printing any information.
In /var/log/messages we can found the following messages (repeated):

Jul 11 17:46:24 cdrc1-2 fenced[4214]: fencing node "cdrc1-1"
Jul 11 17:46:38 cdrc1-2 fenced[4214]: agent "fence_bladecenter" reports: pattern match timed-out at /sbin/fence_bladecenter line 185
Jul 11 17:46:38 cdrc1-2 fenced[4214]: fence "cdrc1-1" failed

If the node 1 is plugged, the node 2 became Active (fenced OK)

Here is the configuration of the fenced (cluster.conf)

        <fence_daemon clean_start="1" post_fail_delay="0" post_join_delay="3"/>
                <clusternode name="cdrc1-1" votes="1">
                                <method name="1">
                                        <device blade="3" name="NBC1"/>
                <clusternode name="cdrc1-2" votes="1">
                                <method name="1">
                                        <device blade="5" name="NBC1"/>
        <cman expected_votes="1" two_node="1"/>
                <fencedevice agent="fence_bladecenter" ipaddr="" login="USERID" name="NBC1" passwd="PASSW0RD"/>

It is a configuration possible to avoid this?
If not, it is possible to deactivate the fenced?

Best regards!
VoIP & Signalling Support

Bull, Architect of an Open World TM
Tél :

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]