<div dir="ltr"><div>Hi, <br><br></div>I have a question regarding &#39;&lt;lrm_resource&gt;&lt;lrm_rsc_op&gt; &#39;op-status attribute getting value 4.<br clear="all"><div><div><br>In my case I have a strange behavior, when resources get those &quot;monitor&quot; operation entries in the CIB with op-status=4, and they do not seem to be called (exec-time=0).<br><br></div><div>What does &#39;op-status&#39; = 4 mean?<br><br></div><div>I would appreciate some elaboration regarding this, since this is interpreted by pacemaker as an error, which causes logs:<br>crm_mon:    error: unpack_rsc_op:    Preventing dbx_head_head from re-starting anywhere: operation monitor failed &#39;not configured&#39; (6)<br></div><div><br></div><div>and I am pretty sure the resource agent was not called (no logs, exec-time=0)<br><br></div><div>There are two aspects of this:<br><br>1) harmless (pacemaker seems to not bother about it), which I guess indicates cancelled monitoring operations:<br></div><div>op-status=4, rc-code=189<br><br></div><div>* Example:<br>&lt;lrm_rsc_op id=&quot;dbx_first_datas_last_failure_0&quot; operation_key=&quot;dbx_first_datas_monitor_0&quot; operation=&quot;monitor&quot; crm-debug-origin=&quot;do_update_resource&quot; crm_feature_set=&quot;3.0.12&quot; transition-key=&quot;38:0:7:c8b63d9d-9c70-4f99-aa1b-e993de6e4739&quot; transition-magic=&quot;4:189;38:0:7:c8b63d9d-9c70-4f99-aa1b-e993de6e4739&quot; on_node=&quot;olegdbx61-vm000001&quot; call-id=&quot;10&quot; rc-code=&quot;189&quot; op-status=&quot;4&quot; interval=&quot;0&quot; last-run=&quot;1495057378&quot; last-rc-change=&quot;1495057378&quot; exec-time=&quot;0&quot; queue-time=&quot;0&quot; op-digest=&quot;f6bd1386a336e8e6ee25ecb651a9efb6&quot;/&gt;<br><br><br></div><div>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 
re-starting anywhere: operation monitor failed &#39;not configured&#39; (6)<br><br></div><div>* Example:<br></div><div>&lt;lrm_rsc_op id=&quot;dbx_head_head_last_failure_0&quot; operation_key=&quot;dbx_head_head_monitor_0&quot; operation=&quot;monitor&quot; crm-debug-origin=&quot;do_update_resource&quot; crm_feature_set=&quot;3.0.12&quot; transition-key=&quot;39:0:7:c8b63d9d-9c70-4f99-aa1b-e993de6e4739&quot; transition-magic=&quot;4:6;39:0:7:c8b63d9d-9c70-4f99-aa1b-e993de6e4739&quot; on_node=&quot;olegdbx61-vm000001&quot; call-id=&quot;999999999&quot; rc-code=&quot;6&quot; op-status=&quot;4&quot; interval=&quot;0&quot; last-run=&quot;1495057389&quot; last-rc-change=&quot;1495057389&quot; exec-time=&quot;0&quot; queue-time=&quot;0&quot; op-digest=&quot;60cdc9db1c5b77e8dba698d3d0c8cda8&quot;/&gt;<br></div><div><br><br></div><div>Could it be some hardware (VM hyperviser) issue?<br></div><div><br></div><div><br>Thanks in advance,<br><br></div><div>-- <br><div class="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></div></div>