[Pacemaker] MySQL after FailOver doesn't allow login

Andrew Beekhof andrew at beekhof.net
Wed May 14 01:19:18 EDT 2014

On 9 May 2014, at 6:09 pm, Denis Witt <denis.witt at concepts-and-training.de> wrote:

> Hi List,
> since the newest update of corosync/pacemaker (running Debian Wheezy so
> versions are 1.1.7-1

1.1.7 came out March 2012 and upstream is now testing 1.1.12... I wouldn't call that new.

> for pacemaker and 1.4.2-3 for corosync) every time
> the services move to another host MySQL reports that everything works
> fine (using lsb-RA). But nobody is allowed to log in to MySQL until a
> restart of MySQL.
> Any ideas what could cause this?

To start with I'd check the mysql logs and/or try the equivalent OCF agent.

> Thanks in advance.
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140514/51a98640/attachment-0003.sig>

More information about the Pacemaker mailing list