Hi,
Andrew Beekhof wrote:
i ran ptest and it wants to start fence1:1 and fence2:1
the CRM probably just needs a little poke to rerun the PE.
try: crm_attribute -n last_cleanup -v `date -r`
ah! that did the trick, but I had to use `date -R` ;)
i cleaned this up for 2.0.6 earlier this
On 5/10/06, Peter Kruse [EMAIL PROTECTED] wrote:
Hi,
Andrew Beekhof wrote:
On 5/9/06, Peter Kruse [EMAIL PROTECTED] wrote:
although cibadmin -Ql -o status does not show the failed resource
anymore. How can I recover from this situation?
cib contents?
Oh, thanks for reminding me (I
On 5/9/06, Peter Kruse [EMAIL PROTECTED] wrote:
Hi,
Andrew Beekhof wrote:
if you want a list of failed resources: crm_mon -1 | grep failed
if you just want the lrm_rsc_op's that failed, look for rc_code != 0
rc_code != 7 (where 7 is LSB for Safely Stopped) in the result of
cibadmin -Ql
Hi,
Andrew Beekhof wrote:
On 5/9/06, Peter Kruse [EMAIL PROTECTED] wrote:
although cibadmin -Ql -o status does not show the failed resource
anymore. How can I recover from this situation?
cib contents?
Oh, thanks for reminding me (I should know by now...)
attached is output of cibadmin
Hello,
it seems that in 2.0.5 the attribute rsc_state to lrm_rsc_op has
disappeared. And has been replaced by rc_code and op_status.
But it is not the same. In order to remove errors in the
cib, so that resources are started again, or nodes can take over
again, I used to do something like this:
Hi,
Andrew Beekhof wrote:
if you want a list of failed resources: crm_mon -1 | grep failed
if you just want the lrm_rsc_op's that failed, look for rc_code != 0
rc_code != 7 (where 7 is LSB for Safely Stopped) in the result of
cibadmin -Ql -o status
Is that also true for fencing resources?
