[Pacemaker] Issue getting mysql to start up with HeartBeat/Pacemaker

Prakash Velayutham prakash.velayutham at cchmc.org
Tue Aug 9 18:53:40 EDT 2011

Could it be that the user that mysql runs as (mysql??) does not have permission to write to the folder /var/run/mysqld? Can you do the following in the system as root and report back?

su - <mysqluser>
touch /var/run/mysqld/test


On Aug 9, 2011, at 6:17 PM, Michael Szilagyi wrote:

> I've recently started taking a look at pacemaker to get some kind of HA in a mysql test environment.  The grouping has a ocf:heartbeat:IPaddr2 and a ocf:heartbeat:mysql monitor in it.  The IP monitor spins up fine and properly jumps around the cluster depending on which node is active.  I'm having issues getting mysql to spin up, however.
> Basically (so far) I've:
> Here is the definitions you can view when doing a crm configure edit:
> primitive p_novaSQL_IP ocf:heartbeat:IPaddr2 \
>         params ip="" nic="eth0" \
>         op monitor interval="10s"
> primitive p_mysql ocf:heartbeat:mysql \
>         params binary="/usr/bin/mysqld_safe" config="/etc/mysql/my.cnf" socket="/var/run/mysqld/mysock.sock" datadir="/var/lib/mysql" \
>         op monitor interval="10s" timeout="30s" \
>         op start interval="0" timeout="120" \
>         op stop interval="0" timeout="120" \
>         meta target-role="Started"
> group g_sqlMonitor p_sql_IP p_mysql
> property $id="cib-bootstrap-options" \
>         dc-version="1.0.9-da7075976b5ff0bee71074385f8fd02f296ec8a3" \
>         cluster-infrastructure="Heartbeat" \
>         stonith-enabled="false" \
>         last-lrm-refresh="1312926142" \
>         no-quorum-policy="ignore"
> Error reported from crm_mon:
> p_novasql_start_0 (node=sql1, call=74, rc=-2, status=Timed Out): unknown exec error
> Error reported from sql (/var/log/mysql/error.log)
> 110809 14:57:22 [ERROR] Can't start server : Bind on unix socket: Permission denied
> 110809 14:57:22 [ERROR] Do you already have another mysqld server running on socket: /var/run/mysqld/mysock.sock ?
> 110809 14:57:22 [ERROR] Aborting
> I've dug around but can't seem to find a resolution to this error.  I've looked at a couple quick & dirty examples for getting mysql up and running with Pacemaker and the above seems to match with the config data.  Any ideas/suggestions would be greatly appreciated.
> -Mike.

More information about the Pacemaker mailing list