[ClusterLabs] Failed to retrieve meta-data for custom ocf resource

Christopher Harvey cwh at eml.cc
Thu Sep 29 12:41:57 EDT 2016

On Thu, Sep 29, 2016, at 12:20 PM, Jan Pokorný wrote:
> On 28/09/16 16:55 -0500, Ken Gaillot wrote:
> > On 09/28/2016 04:04 PM, Christopher Harvey wrote:
> >> My corosync/pacemaker logs are seeing a bunch of messages like the
> >> following:
> >> 
> >> Sep 22 14:50:36 [1346] node-132-60       crmd:     info:
> >> action_synced_wait:     Managed MsgBB-Active_meta-data_0 process 15613
> >> exited with rc=4
> Another possibility is that "execvp" call, i.e., means to run this very
> agent, failed at a fundemental level (could also be due to kernel's
> security modules like SELinux, seccomp, etc. as already mentioned).

I don't have seccomp or SELinux.

> Do other agents work flawlessly for you?

I only have my custom agent. All actions work except meta-data. In fact,
I put the following at the very top of my resource agent:
#! /bin/bash
touch /tmp/yeah
echo "yeah running ${@}" >> /tmp/yeah

and the 'yeah' file gets filled with monitor/start/stop, but not
meta-data. I think something is failing at the  execvp() level. I'm
seeing useful looking trace logs in the code, but can't enable them
right now. I have:

but I'm not seeing the pacemaker.log anywhere, and corosync.log only has
info and higher.

More information about the Users mailing list