On Mon, May 18, 2009 at 8:12 PM, Dejan Muhamedagic <[email protected]> wrote: > > The status operation of the LSB named RA timed out, for whatever > reason (don't know in which way it is implemented). If you think > it's not, then you ran into some really serious bug there. Also, > the dhcp stop action failed, that's dangerous, leaves the > resource in an unknown state. Make sure that all your RAs behave! >
Yeah, that's strange. I checked through the old logs, and heartbeat didn't show any monitoring activity until today. I went ahead and disabled monitoring on services that aren't essential for the cluster to continue to operate. Hopefully this will prevent auxiliary services from causing a failover. > If you move to 2.99.x, then you'll also have to move to > pacemaker. Not a bad thing, if you can afford it. Otherwise, use > at least 2.1.4. > Yeah, I'll have to eval 2.99.x at some point. We're on 2.1.3 now, so I'll see what 2.1.4 fixes. Thanks for your response. -- Jiann-Ming Su "I have to decide between two equally frightening options. If I wanted to do that, I'd vote." --Duckman "The system's broke, Hank. The election baby has peed in the bath water. You got to throw 'em both out." --Dale Gribble "Those who vote decide nothing. Those who count the votes decide everything.” --Joseph Stalin _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
