[Pacemaker] Monitor and standby

Andrey Groshev greenx at yandex.ru
Wed Jul 3 10:44:17 UTC 2013



03.07.2013, 14:26, "Denis Witt" <denis.witt at concepts-and-training.de>:
> Hi List,
>
> we have a two node cluster (test1-node1, test1-node2) with an additional
> quorum node (test1). On all nodes MySQL is running. test1-node1 and
> test1-node2 sharing the MySQL-Database via DRBD, so only one Node
> should run MySQL. On test1 there is a MySQL-Slave connected to
> test1-node1/test1-node2. test1 is always in Standby-Mode.
>
> The problem is now that the MySQL-Slave on test1 is shut down by crmd:
>
> Jul  3 12:05:12 test2 crmd: [5945]: info: te_rsc_command: Initiating action 22: monitor p_mysql_monitor_0 on test2 (local)
> Jul  3 12:05:14 test2 pengine: [5944]: ERROR: native_create_actions: Resource p_mysql (lsb::mysql) is active on 2 nodes attempting recovery
> Jul  3 12:05:14 test2 pengine: [5944]: notice: LogActions: Restart p_mysql#011(Started test2-node1)
> Jul  3 12:05:15 test2 crmd: [5945]: info: te_rsc_command: Initiating action 54: stop p_mysql_stop_0 on test2 (local)
>
> From my understanding this shouldn't happen as test1 was set to standby
> before:
>
> Jul  3 12:04:48 test2 cib: [5940]: info: cib:diff: +           <nvpair id="nodes-test2-standby" name="standby" value="on" />
>
> How could we solve this?
>

Begin you wrote - test1-node1, test1-node2, test1... 
In log test2, test2-node1, this is right?
Maybe hostnames wrong?

> Thanks in advance.
>
> Best regards
> Denis Witt
>
> _______________________________________________
> 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




More information about the Pacemaker mailing list