Dejan, looks like a LRM bug to me... fixed anything like this since 2.0.8? On Wed, Mar 26, 2008 at 1:29 PM, Manas Garg <[EMAIL PROTECTED]> wrote: > Hello, > > We are using heartbeat version 2.0.8 on a Linux machine with 2 dual core > CPUs and 8 GB RAM. We saw a strange thing sometime back. Heartbeat started > one resource and immediately declared it as timed out. The actual timeout > set in the CIB is 15 seconds.
Timestamps pretty much confirm exactly what you're saying... Mar 18 16:31:04 lansighttwo crmd: [8246]: info: do_lrm_rsc_op: Performing op=Admin-Notify_start_0 key=30:1:69e21efe-2a8c-46bf-ab1f-b60381d460a7) [snip] Mar 18 16:31:04 lansighttwo lrmd: [8243]: WARN: on_op_timeout_expired: TIMEOUT: operation start[30] on ocf::AdminNotify::Admin-Notify for client 8246, its parameters: resource_failure_stickiness=[-100] CRM_meta_op_target_rc=[7] CRM_meta_id=[17] CRM_meta_timeout=[30000] CRM_meta_on_fail=[restart] crm_feature_set=[1.0.7] CRM_meta_name. Mar 18 16:31:04 lansighttwo crmd: [8246]: ERROR: process_lrm_event: LRM operation Admin-Notify_start_0 (30) Timed Out (timeout=30000ms) _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
