[Pacemaker] Resource active on both nodes

[Andrew Beekhof]

On Fri, Jul 6, 2012 at 4:47 AM, Andrew Widdersheim
<awiddersheim at hotmail.com> wrote:
> I'm seeing messages similar to the following:
>
> Jul  5 14:34:06 server1 pengine: [423]: notice: unpack_rsc_op: Operation
> p_syslog-ng_monitor_0 found resource p_syslog-ng active on server2
> Jul  5 14:34:06 server1 pengine: [423]: notice: unpack_rsc_op: Operation
> p_bacula_monitor_0 found resource p_bacula active on server2
>
> The cluster is running fine currently and none of these resources are
> started on the server2 (currently the passive node) so I'm not clear on why
> I'm seeing these messages.

Most likely, the OS is starting these automatically when the machine boots.
>
> All of the start and stop scripts are LSB compliant per:
> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/ap-lsb.html
>
> No resource failures when doing crm_mon -rf.
>
> Is it possible at some point these resources were active on both nodes and
> was corrected but theses messages persist? Also none of these resources are
> set to start at boot or anything of that nature.
>
> OS: RHEL6
> Pacemaker: 1.1.5
> Heartbeat: 3.0.5
>
> _______________________________________________
> 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
>