On 10/29/07, Junko IKEDA <[EMAIL PROTECTED]> wrote: > > > if it's LRM_RSC_BUSY, > > > a fail count would be increased, > > > and a return code was set as 14 (EXECRA_STATUS_UNKNOWN ?). > > > > That should not have anything to do with it. If the resource is > > busy, the requested operation will be postponed until it becomes > > idle. The CRM handles such a situation. > > Do you mean that if RA is busy, CRM will wait until it becomes idle?
No, we just fire off operations and let the lrmd tell us when they're done. > It seems that CRM doesn't wait. > > lrmd[9049]: 2007/10/29_12:47:35 debug: on_msg_get_state:state of rsc > prmDummy is LRM_RSC_BUSY > crmd[9136]: 2007/10/29_12:47:35 WARN: msg_to_op(1173): failed to get the > value of field lrm_opstatus from a ha_msg > ... > crmd[9136]: 2007/10/29_12:47:35 WARN: msg_to_op(1173): failed to get the > value of field lfailcount: Updating failcount for prmDummy on > 9d9ca527-cea9-470c-9e03-e49fe5630bba after failed monitor: rc=14 Thats the lrm client library by the looks of it (I don't see that function anywhere in the crm), I wonder what failcount its modifying. Possibly a spelling mistake too "lfailcount" > > A resource is busy whenever there's an operation running, i.e. > > such as monitor. Idle is the opposite. > > I used a modified Dummy resource to emulate a delay of monitoring operation. > This RA is calling "sleep 50" immediately after monitoring. > (see attached Dummy RA) > I wonder it might cause RA's busy status. > > Thanks, > Junko > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
