<div dir="ltr">Hi all:<div><br></div><div>In July, list member Ken Gaillot reported occasional nonsensical resource agent errors using Pacemaker (<a href="http://oss.clusterlabs.org/pipermail/pacemaker/2014-July/022231.html">http://oss.clusterlabs.org/pipermail/pacemaker/2014-July/022231.html</a>).</div><div><br></div><div>We're seeing similar issues with our install. We have a 2 node corosync/pacemaker failover configuration that is using the <span style="color:rgb(0,0,0);white-space:pre-wrap">ocf:heartbeat:IPaddr2 resource agent extensively. About once a week, we'll get an error like this, out of the blue:</span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap"><br></span></div><div><span style="color:rgb(0,0,0);white-space:pre-wrap"> </span><font color="#000000"><span style="white-space:pre-wrap">Nov 1 05:23:57 lb02 IPaddr2(anon_ip)[32312]: ERROR: Setup problem: couldn't find command: ip</span></font></div><div><br></div><div>It goes without saying that the ip command hasn't gone anywhere and all the paths are configured correctly.</div><div><br></div><div>We're currently running 1.1.10-14.el6_5.3-368c726 under CentOS 6 x86_64 inside of a xen container.</div><div><br></div><div>Any thoughts from folks on what might be happening or how we can get additional debug information to help figure out what's triggering this?</div><div><br></div><div>Best,<br>-- <br><div class="gmail_signature">Patrick Michael Kane<br><<a href="mailto:pmk@wawd.com">pmk@wawd.com</a>></div>
</div></div>