Thanks Dave! Now I know what my problem is. Now I'm trying to use fence_brocade as my fencing method, and I have this error when I simulate a failed node, or when I run the command fence_brocade: fence_brocade Can't locate Net/Telnet.pm in @INC (@INC contains: /usr/lib/perl5/5.8.5/i386-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.2/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl/5.8.4 /usr/lib/perl5/site_perl/5.8.3 /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.4/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl/5.8.4 /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl/5.8.2 /usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl .) at /sbin/fence_brocade line 17. BEGIN failed--compilation aborted at /sbin/fence_brocade line 17. Please help. Regards, Antonio Rodriguez -----Original Message----- From: David Teigland [mailto:teigland@xxxxxxxxxx] Sent: Wednesday, May 25, 2005 5:10 PM To: Rodriguez, Antonio Cc: linux-cluster@xxxxxxxxxx Subject: Re: RHEL4AS w/ cvs RHEL4 branch On Wed, May 25, 2005 at 04:54:16PM +0800, Rodriguez, Antonio wrote: > Thanks for the quick reply. > > Yes, my cluster.conf contains this line (required in two node cluster > configuration). > <cman two_node="1" expected_votes="1"> > </cman> > > There's also a fencing messages on the surviving node, saying that the > failed node should be restarted before any recovery can proceed. Waiting > for the node to rejoin the cluster or manual acknowledgement... You should run 'fence_ack_manual' on the surviving node (you've obviously just restarted the failed node by pressing its power button.) > Does this mean that I cannot use the surviving node to host my resources > while my other node is fenced? > > Clustat says that my cluster is still qourate even with one node > remaining. The special two_node option allows the cluster to have quorum even though there's only one node remaining. Everything should run normally on the surviving node after you do the manual ack. Using SAN fencing with the brocade will eliminate this manual step. Dave -- Linux-cluster@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/linux-cluster
