Am Dienstag, 26. Mai 2009 12:12:38 schrieb Andrew Beekhof: > On Tue, May 26, 2009 at 12:06 PM, Michael Schwartzkopff > > <[email protected]> wrote: > > Am Dienstag, 26. Mai 2009 10:26:46 schrieb Andrew Beekhof: > >> On Tue, May 26, 2009 at 10:19 AM, Michael Schwartzkopff > >> > >> <[email protected]> wrote: > >> > Am Dienstag, 26. Mai 2009 09:42:53 schrieb Andrew Beekhof: > >> > >> [snip] > >> > >> >> The cluster can't react to the current event until all the actions it > >> >> took in order to react to the previous event have finished. > >> >> This is what is happening here and its the resDRBD:1_monitor_20000 > >> >> action that we're blocking on. > >> >> > >> >> May 26 08:18:14 mom2 crmd: [2808]: info: te_rsc_command: Initiating > >> >> action 13: monitor resDRBD:1_monitor_20000 on mom2 (local) > >> >> > >> >> May 26 08:19:14 mom2 crmd: [2808]: info: process_lrm_event: LRM > >> >> operation resDRBD:1_monitor_20000 (call=65, rc=0, cib-update=173, > >> >> confirmed=false) complete ok > >> > > >> > OK. Your answer leads me to the next question: What causes the monitor > >> > operation to take 1 minute? > >> > >> No idea, but the answer will be in the drbd RA > > > > Hi, > > > > The problem is in the CRM, not in the RA. I configured a pingd clone and > > this resource behaves identically. One minute timeout when one node is > > set to standby. See log attached. I file a bugreport. > > If anything its in the lrmd - since thats what the CRM is waiting for.
I filed bug #2122 -- Dr. Michael Schwartzkopff MultiNET Services GmbH Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany Tel: +49 - 89 - 45 69 11 0 Fax: +49 - 89 - 45 69 11 21 mob: +49 - 174 - 343 28 75 mail: [email protected] web: www.multinet.de Sitz der Gesellschaft: 85630 Grasbrunn Registergericht: Amtsgericht München HRB 114375 Geschäftsführer: Günter Jurgeneit, Hubert Martens --- PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B Skype: misch42 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
