[Pacemaker] Occasional nonsensical resource agent errors, redux
Andrew Beekhof
andrew at beekhof.net
Tue Nov 4 21:44:06 UTC 2014
> On 5 Nov 2014, at 4:21 am, Ken Gaillot <kjgaillo at gleim.com> wrote:
>
>>> Sep 13 20:17:07 pisces lrmd: [3509]: info: RA output:
>>> (pan:monitor:stderr) /usr/lib/ocf/resource.d//heartbeat/Xen: 71: local:
>>
>> This "local" seems to be from ocf-binaries:have_binary():
>>
>> 71 local bin=`echo $1 | sed -e 's/ -.*//'`
>
> Agreed, nothing unusual there, reinforces suspicion of memory corruption.
>
>>> Sep 13 20:17:07 pisces lrmd: [3509]: info: RA output:
>>> (pan:monitor:stderr) en-destroy: bad variable name
>>> Sep 13 20:17:07 pisces lrmd: [3509]: info: RA output: (pan:monitor:stderr)
>>> Sep 13 20:17:07 pisces lrmd: [3509]: info: operation monitor[21] on pan
>>> for client 3512: pid 455 exited with return code 2
Not that pacemaker couldn't cause this, but I'm curious to know if anyone has seen this on bare metal...
VMs, with their backing stores and COW overlays seem like a reasonable candidate based on my experiences.
More information about the Pacemaker
mailing list