On 9/3/07, Dejan Muhamedagic <[EMAIL PROTECTED]> wrote: > Hi, > > On Sun, Sep 02, 2007 at 11:03:47AM +0200, Michael Schwartzkopff wrote: > > Hi, > > > > When I use the GUI > > - add an apache/ocf resource, but do not start it and > > - remove it immedeately again > > > > I still see it in the LRM resources, once per node: > > cibadmin -Q -o status > > (...) > > <lrm_resources> > > <lrm_resource id="resource_apache" type="apache" class="ocf" > > provider="heartbeat"> > > <lrm_rsc_op id="resource_apache_monitor_0" operation="monitor" > > crm-debug-origin="do_update_resource" > > transition_key="3:21:d3e0b6cb-0d0d-4b2b-8220-ab6bd96f1798" > > transition_magic="0:7;3:21:d3e0b6cb-0d0d-4b2b-8220-ab6bd96f1798" > > call_id="14" crm_feature_set="1.0.9" rc_code="7" op_status="0" > > interval="0" op_digest="02e4774ae092e0e208c54ca2d084a1c7"/> > > </lrm_resource> > > </lrm_resources> > > (...) > > > > Please could anybody explain why these resources still appear in my CIB?
Because the resource's action history is still in the LRM > > This is most probably a probe monitor operation. nod > > Is there any other automatic removal / cleanup process other than manual > > invoking: > > crm_resource -C -r resource_apache thats the best way > > You can set remove-after-stop to true in the > cluster_property_set. Though I'm not sure if that would help in > the case you mentioned. it would, but its not a very well tested option (if you use it and find problems i'll fix them asap) _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
