<div dir="ltr">Thanks, <br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 18, 2017 at 4:37 PM, Ken Gaillot <span dir="ltr"><<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 05/17/2017 06:10 PM, Radoslaw Garbacz wrote:<br>
> Hi,<br>
><br>
> I have a question regarding '<lrm_resource><lrm_rsc_op> 'op-status<br>
> attribute getting value 4.<br>
><br>
> In my case I have a strange behavior, when resources get those "monitor"<br>
> operation entries in the CIB with op-status=4, and they do not seem to<br>
> be called (exec-time=0).<br>
><br>
> What does 'op-status' = 4 mean?<br>
<br>
</span>The action had an error status<br>
<span class=""><br>
><br>
> I would appreciate some elaboration regarding this, since this is<br>
> interpreted by pacemaker as an error, which causes logs:<br>
> crm_mon: error: unpack_rsc_op: Preventing dbx_head_head from<br>
> re-starting anywhere: operation monitor failed 'not configured' (6)<br>
<br>
</span>The rc-code="6" is the more interesting number; it's the result returned<br>
by the resource agent. As you can see above, it means "not configured".<br>
What that means exactly is up to the resource agent's interpretation.<br>
<span class=""><br>
> and I am pretty sure the resource agent was not called (no logs,<br>
> exec-time=0)<br>
<br>
</span>Normally this could only come from the resource agent.<br>
<br>
However there are two cases where pacemaker generates this error itself:<br>
if the resource definition in the CIB is invalid; and if your version of<br>
pacemaker was compiled with support for reading sensitive parameter<br>
values from a file, but that file could not be read.<br>
<br>
It doesn't sound like your case is either one of those though, since<br>
they would prevent the resource from even starting. Most likely it's<br>
coming from the resource agent. I'd look at the resource agent source<br>
code and see where it can return OCF_ERR_CONFIGURED.<br>
<span class=""><br>
> There are two aspects of this:<br>
><br>
> 1) harmless (pacemaker seems to not bother about it), which I guess<br>
> indicates cancelled monitoring operations:<br>
> op-status=4, rc-code=189<br>
<br>
</span>This error means the connection between the crmd and lrmd daemons was<br>
lost -- most commonly, that shows up for operations that were pending at<br>
shutdown.<br>
<div><div class="h5"><br>
><br>
> * Example:<br>
> <lrm_rsc_op id="dbx_first_datas_last_<wbr>failure_0"<br>
> operation_key="dbx_first_<wbr>datas_monitor_0" operation="monitor"<br>
> crm-debug-origin="do_update_<wbr>resource" crm_feature_set="3.0.12"<br>
> transition-key="38:0:7:<wbr>c8b63d9d-9c70-4f99-aa1b-<wbr>e993de6e4739"<br>
> transition-magic="4:189;38:0:<wbr>7:c8b63d9d-9c70-4f99-aa1b-<wbr>e993de6e4739"<br>
> on_node="olegdbx61-vm000001" call-id="10" rc-code="189" op-status="4"<br>
> interval="0" last-run="1495057378" last-rc-change="1495057378"<br>
> exec-time="0" queue-time="0" op-digest="<wbr>f6bd1386a336e8e6ee25ecb651a9ef<wbr>b6"/><br>
><br>
><br>
> 2) error level one (op-status=4, rc-code=6), which generates logs:<br>
> crm_mon: error: unpack_rsc_op: Preventing dbx_head_head from<br>
> re-starting anywhere: operation monitor failed 'not configured' (6)<br>
><br>
> * Example:<br>
> <lrm_rsc_op id="dbx_head_head_last_<wbr>failure_0"<br>
> operation_key="dbx_head_head_<wbr>monitor_0" operation="monitor"<br>
> crm-debug-origin="do_update_<wbr>resource" crm_feature_set="3.0.12"<br>
> transition-key="39:0:7:<wbr>c8b63d9d-9c70-4f99-aa1b-<wbr>e993de6e4739"<br>
> transition-magic="4:6;39:0:7:<wbr>c8b63d9d-9c70-4f99-aa1b-<wbr>e993de6e4739"<br>
> on_node="olegdbx61-vm000001" call-id="999999999" rc-code="6"<br>
> op-status="4" interval="0" last-run="1495057389"<br>
> last-rc-change="1495057389" exec-time="0" queue-time="0"<br>
> op-digest="<wbr>60cdc9db1c5b77e8dba698d3d0c8cd<wbr>a8"/><br>
><br>
><br>
> Could it be some hardware (VM hyperviser) issue?<br>
><br>
><br>
> Thanks in advance,<br>
><br>
> --<br>
> Best Regards,<br>
><br>
> Radoslaw Garbacz<br>
> XtremeData Incorporated<br>
<br>
</div></div>______________________________<wbr>_________________<br>
Users mailing list: <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
<a href="http://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.clusterlabs.org/<wbr>mailman/listinfo/users</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/<wbr>doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Best Regards,<br><br>Radoslaw Garbacz<br></div>XtremeData Incorporated<br></div></div></div></div>
</div>