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

Re: [Linux-cluster] Issue with mysql service in RHEL6.2 cluster



Any more suggestions on this?

 

From: linux-cluster-bounces redhat com [mailto:linux-cluster-bounces redhat com] On Behalf Of Roka, Rajendra
Sent: Tuesday, 10 January 2012 11:49 AM
To: linux-cluster redhat com
Subject: Re: [Linux-cluster] Issue with mysql service in RHEL6.2 cluster

 

 

I have changed the resources and service in cluster.conf as follows:

 

<resources>

                        <ip address="10.26.240.95/24" monitor_link="on" sleeptime="2"/>

                        <mysql config_file="/etc/my.cnf" listen_address="10.26.24.95" name="mysql" shutdown_wait="60" startup_wait="60"/>

                        <netfs export="/nfs/mysql" force_unmount="on" fstype="nfs" host="10.26.240.190" mountpoint="/var/lib/mysql" name="storage" no_unmount="on"/>

                </resources>

                <service autostart="1" domain="atp_failover" exclusive="0" name="mysql" recovery="relocate">

                        <ip ref="10.26.240.95/24"/>

                        <netfs ref="storage"/>

                        <mysql ref="mysql"/>

                </service>

 

But no luck with the following message:

 

Jan 10 11:42:57 atp-wwdev1 modcluster: Starting service: mysql on node

Jan 10 11:42:57 atp-wwdev1 rgmanager[1690]: Starting stopped service service:mysql

Jan 10 11:42:58 atp-wwdev1 rgmanager[5252]: Adding IPv4 address 10.26.240.95/24 to eth0

Jan 10 11:43:01 atp-wwdev1 rgmanager[5401]: Starting Service mysql:mysql

Jan 10 11:44:01 atp-wwdev1 rgmanager[5657]: Starting Service mysql:mysql > Failed - Timeout Error

Jan 10 11:44:01 atp-wwdev1 rgmanager[1690]: start on mysql "mysql" returned 1 (generic error)

Jan 10 11:44:02 atp-wwdev1 rgmanager[1690]: #68: Failed to start service:mysql; return value: 1

Jan 10 11:44:02 atp-wwdev1 rgmanager[1690]: Stopping service service:mysql

Jan 10 11:44:02 atp-wwdev1 rgmanager[5742]: Stopping Service mysql:mysql

Jan 10 11:44:02 atp-wwdev1 rgmanager[5764]: Checking Existence Of File /var/run/cluster/mysql/mysql:mysql.pid [mysql:mysql] > Failed - File Doesn't Exist

Jan 10 11:44:02 atp-wwdev1 rgmanager[5786]: Stopping Service mysql:mysql > Succeed

Jan 10 11:44:02 atp-wwdev1 rgmanager[5837]: Removing IPv4 address 10.26.240.95/24 from eth0

Jan 10 11:44:04 atp-wwdev1 rgmanager[5924]: unmounting /var/lib/mysql

Jan 10 11:44:04 atp-wwdev1 rgmanager[1690]: Service service:mysql is recovering

Jan 10 11:44:04 atp-wwdev1 rgmanager[1690]: #71: Relocating failed service service:mysql

Jan 10 11:45:14 atp-wwdev1 rgmanager[1690]: Service service:mysql is stopped

 

Also changed the my.conf to:

 

pid-file=/var/run/cluster/mysql/mysql.pid

 

Cheers

 

 

From: linux-cluster-bounces redhat com [mailto:linux-cluster-bounces redhat com] On Behalf Of Ryan Mitchell
Sent: Tuesday, 10 January 2012 10:12 AM
To: linux-cluster redhat com
Subject: Re: [Linux-cluster] Issue with mysql service in RHEL6.2 cluster

 

On 01/10/2012 07:57 AM, Roka, Rajendra wrote:

I am having issue with mysql service in RHEL6.2 cluster. While starting service I receive the following error in /var/log/message

 

Jan 10 08:47:52 atp-wwdev1 rgmanager[6015]: Starting Service mysql:mysql

Jan 10 08:47:54 atp-wwdev1 rgmanager[6096]: Starting Service mysql:mysql > Failed - Timeout Error

Jan 10 08:47:54 atp-wwdev1 rgmanager[1842]: start on mysql "mysql" returned 1 (generic error)

 

I'm pretty sure the first problem is that mysql doesn't start before the script times out.  All subsequent errors are trying to clean up from the failed start and can be ignored.  There won't be a pid file if the service did not start or if it was cleanly shut down outside of rgmanager.  Try increasing the startup_wait (something large until you find its successful, like 60).  Its currently waiting 2 seconds.

Also, I don't think you want to have the VIP and the service that uses it (mysql) in different services.  They should be in the same service, because they always have to run on the same node (they aren't independent).  Same goes for the filesystem resource if that is required by MYSQL.  Perhaps something like the following?:

                <resources>

                        <ip address="10.26.240.95/24" monitor_link="on" sleeptime="2"/>

                        <netfs export="/nfs/mysql" force_unmount="on" fstype="nfs" host="10.26.240.190" mountpoint="/var/lib/mysql" name="filesystem" no_unmount="on"/>

                        <mysql config_file="/etc/my.cnf" listen_address="10.26.240.95" name="mysql" shutdown_wait="60" startup_wait="60"/>

                </resources>

                <service autostart="1" domain="atp_failover" exclusive="0" name="database" recovery="relocate">

                        <ip ref="10.26.240.95/24"/>

                        <netfs ref="filesystem"/>

                        <mysql ref="mysql"/>

                </service>


Lastly, you have created a fence device but you haven't assigned it to the nodes so they currently have no fencing devices.  Make sure you do that and test fencing before doing anything important with this cluster.

Regards,

Ryan Mitchell
Software Maintenance Engineer
Support Engineering Group
Red Hat, Inc.

Important Notice:
This message and its attachments are confidential and may contain information which is protected by copyright. It is intended solely for the named addressee. If you are not the authorised recipient (or responsible for delivery of the message to the authorised recipient), you must not use, disclose, print, copy or deliver this message or its attachments to anyone. If you receive this email in error, please contact the sender immediately and permanently delete this message and its attachments from your system. 
Any content of this message and its attachments that does not relate to the official business of Pacific Magazines Pty Limited must be taken not to have been sent or endorsed by it. No representation is made that this email or its attachments are without defect or that the contents express views other than those of the sender.
 
Please consider the environment - do you really need to print this email?
 
 
 
Important Notice:
This message and its attachments are confidential and may contain information which is protected by copyright. It is intended solely for the named addressee. If you are not the authorised recipient (or responsible for delivery of the message to the authorised recipient), you must not use, disclose, print, copy or deliver this message or its attachments to anyone. If you receive this email in error, please contact the sender immediately and permanently delete this message and its attachments from your system. 
Any content of this message and its attachments that does not relate to the official business of Pacific Magazines Pty Limited must be taken not to have been sent or endorsed by it. No representation is made that this email or its attachments are without defect or that the contents express views other than those of the sender.

Please consider the environment - do you really need to print this email?




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