[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



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.


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