[Pacemaker] mysql cluster resource agent failed to start

[Michael Schwartzkopff]

> Hello everybody,
> 
> I have here several MySQL failover clusters with pacemaker and corosync at
> Ubuntu 10.04 LTS running. After a problem with a crashed cluster cib, I
> decided to reinstall one of the cluster with Ubuntu 12.04 LTS. I always
> have used the packages of the distribution for the cluster. The new
> Installation have the same configuration of the cluster as the old one.
> Now everything seemed to work well. Only the mysql resource agent have now
> a strange behaviour. If I startet a resource group, pacemaker started the
> mysql database and after one or two seconds he sends a shutdown signal to
> the mysql agent. I have tried to start the mysql resource agent at the
> bash with the same command options as pacemaker would do. If I do this,
> the mysql db starts witout problems. In the log files of the mysql db, I
> can see that it is a graceful shutdown. Unfortunately are on this cluster
> 16 service groups. If I put the cluster in debug mode, the whole server is
> getting very slow. So I had to abort the debug mode, to keep the databases
> running.
> 
> This is the configuration of the mysql resource agent:
> primitive mysqltest03-db ocf:heartbeat:mysql \
>         params binary="/srv/mysql-server/releases/mysql/bin/mysqld"
> config="/srv/mysql/mysqltest03/admin/etc/my.cnf" user="mysql"
> group="mysql" datadir="/srv/mysql/mysqltest03/data"
> log="/srv/mysql/mysqltest03/admin/log/mysqld.log"
> pid="/srv/mysql/mysqltest03/admin/run/mysqld.pid"
> socket="/srv/mysql/mysqltest03/admin/run/mysqld.sock" test_passwd="xxx"
> test_user="xxx" test_table="mysql.user"
> additional_parameters="--bind-address=xx.xx.xx.xx" \ op start interval="0"
> timeout="120s" \
>         op stop interval="0" timeout="120s" \
>         op monitor interval="30s" timeout="60s" \
>         meta is-managed="true" target-role="started"
> 
> 
> Is anybody here, who can give me a hint, why pacemaker always sends a stop
> signal after one second?
> 
> Thanks,
> 
> Josef

the truth is in the logs. Read the logs to find out why pacemaker does behave 
like this or paste the relevant parts of the logs somewhere and send the link 
to this list. So we could help you.

Greetings,

-- 
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120817/0d8998fb/attachment-0003.sig>