Hi, Attach the /var/log/messages or rgmanager logs to get more info ..
On Fri, Feb 5, 2010 at 10:10 AM, Kukkala Prasad <[email protected]> wrote: > Hi Charles, > > Here is the configuration details. > > <?xml version="1.0"?> > <cluster alias="mysqlha" config_version="80" name="mysqlha"> > <fence_daemon post_fail_delay="0" post_join_delay="3"/> > <clusternodes> > <clusternode name="srv-int-rs4.ourdomain.com" nodeid="1" > votes="1"> > <fence> > <method name="1"> > <device name="vb4-rs4"/> > </method> > </fence> > </clusternode> > <clusternode name="srv-int-rs5.ourdomain.com" nodeid="2" > votes="1"> > <fence> > <method name="1"> > <device name="vb2-rs5"/> > </method> > </fence> > </clusternode> > <clusternode name="srv-int-rs6.ourdomain.com" nodeid="3" > votes="1"> > <fence> > <method name="1"> > <device name="perf10-rs6"/> > </method> > </fence> > </clusternode> > </clusternodes> > <cman/> > <fencedevices> > <fencedevice agent="fence_ilo" hostname="ilo-int-vb4" > login="admin" name="vb4-rs4" passwd="*****"/> > <fencedevice agent="fence_ilo" hostname="ilo-int-vb2" > login="admin" name="vb2-rs5" passwd="*****"/> > <fencedevice agent="fence_ilo" hostname="ilo-int-perf10" > login="admin" name="perf10-rs6" passwd="*****"/> > </fencedevices> > <rm> > <failoverdomains> > <failoverdomain name="faiodom1" ordered="0" > restricted="1"> > <failoverdomainnode > name="srv-int-rs4.ourdomain.com" priority="1"/> > <failoverdomainnode > name="srv-int-rs5.ourdomain.com" priority="1"/> > </failoverdomain> > </failoverdomains> > <resources> > <lvm lv_name="SANLogVol01" name="SAN Volume" > vg_name="SANVolGroup01"/> > <fs device="/dev/SANVolGroup01/SANLogVol01" > force_fsck="0" force_unmount="0" fsid="4190" fstype="ext3" > mountpoint="/mysqldb" name="sanvolume" options="" self_fence="0"/> > <ip address="12.151.50.91" monitor_link="1"/> > <mysql config_file="/etc/my.cnf" > listen_address="12.151.50.91" mysql_options="" name="mysql" > shutdown_wait="5"/> > </resources> > <service autostart="1" domain="faiodom1" name="mysql-service" > recovery="relocate"> > <lvm ref="SAN Volume"/> > <fs ref="sanvolume"/> > <ip ref="12.151.50.91"/> > <mysql ref="mysql"/> > </service> > </rm> > </cluster> > > Regards, > Prasad. > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Charles Riley > Sent: Thursday, February 04, 2010 8:59 PM > To: linux clustering > Subject: Re: [Linux-cluster] Failover not happening when SAN connectivity > failed > > <Null pointer error> > (you don't really expect someone to help you with no information regarding > your configuration, do you?) > > Charles > > Charles Riley > eRAD, Inc. > > > > ----- Original Message ----- > From: "Kukkala Prasad" <[email protected]> > To: [email protected] > Sent: Thursday, February 4, 2010 5:42:35 AM GMT -05:00 US/Canada Eastern > Subject: [Linux-cluster] Failover not happening when SAN connectivity failed > > > > > > Hi All, > > > > We have a cluster setup with Redhat Cluster Suite on RHEL5 OS. > > SAN is one of the resource configured in the cluster. > > We observed that if the SAN connectivity is lost on a given node then > resources are not getting failovered to second node. How to resolve this > problem? > > > > Regards, > > Prasad. > > The information contained in this communication is confidential, intended > solely for the use of the individual or entity to whom it is addressed and > may be legally privileged and protected by professional secrecy. Access to > this message by anyone else is unauthorized. If you are not the intended > recipient, any disclosure, copying, or distribution of the message, or any > action or omission taken by you in reliance on it is prohibited and may be > unlawful. Please immediately contact the sender if you have received this > message in error. This email does not constitute any commitment from Cordys > Holding BV or any of its subsidiaries except when expressly agreed in a > written agreement between the intended recipient and Cordys Holding BV or its > subsidiaries. Cordys is neither liable for the proper and complete > transmission of the information contained in this communication nor for any > delay in its receipt. Cordys does not guarantee that the integrity of this > communication has been m! > aintained nor that the communication is free of viruses, interceptions or > interference. If you are not the intended recipient of this communication > please return the communication to the sender and delete and destroy all > copies. > > -- > Linux-cluster mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/linux-cluster > > -- > Linux-cluster mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/linux-cluster > > -- > Linux-cluster mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/linux-cluster > -- Linux-cluster mailing list [email protected] https://www.redhat.com/mailman/listinfo/linux-cluster
