On 12 Sep 2013, at 3:44 am, Lindsay Todd wrote:
> What I am seeing in the syslog are messages like:
>
> Sep 11 13:19:52 db02 pacemaker_remoted[1736]: notice: operation_finished:
> p-my
> sql_monitor_2:19398:stderr [ 2013/09/11_13:19:52 INFO: MySQL monitor
> succeed
> ed ]
> Sep 11 13:20
What I am seeing in the syslog are messages like:
Sep 11 13:19:52 db02 pacemaker_remoted[1736]: notice: operation_finished:
p-my
sql_monitor_2:19398:stderr [ 2013/09/11_13:19:52 INFO: MySQL monitor
succeed
ed ]
Sep 11 13:20:08 cvmh03 pengine[4832]: warning: unpack_rsc_op_failure:
Processin
- Original Message -
> From: "Lindsay Todd"
> To: "The Pacemaker cluster resource manager"
> Sent: Tuesday, September 3, 2013 3:18:17 PM
> Subject: [Pacemaker] asymmetric clusters, remote nodes, and monitor
> operations
>
> We've bee
Hello Andrew,
I do have the symmetric-cluster=false property.
Since this is possibly a bug, I've submitted a crm_report as bug #5176, so
not only should you have a snapshot of logging information, you can also
see the configuration. Thanks.
/Lindsay
On Wed, Sep 4, 2013 at 12:49 AM, Andrew Bee
On 04/09/2013, at 6:18 AM, Lindsay Todd wrote:
> We've been attempting to set up an asymmetric pacemaker cluster using remote
> cluster nodes, with pacemaker 1.1.10 (actually, building from git lately,
> currently at a4eb44f). We use location constraints to enable resources to
> start on nod
We've been attempting to set up an asymmetric pacemaker cluster using
remote cluster nodes, with pacemaker 1.1.10 (actually, building from git
lately, currently at a4eb44f). We use location constraints to enable
resources to start on nodes they should start on, and rely on asymmetry to
otherwise k
