We're running heartbeat 2.0.8 under RHEL4, and in our QA environment, were seeing this sequence of log messages:
Feb 12 21:18:23 vdev-3230 heartbeat: [6941]: ERROR: Message hist queue is filling up (200 messages in queue) Feb 12 21:18:54 vdev-3230 last message repeated 61 times Feb 12 21:22:58 vdev-3230 last message repeated 122 times Feb 12 21:23:33 vdev-3230 last message repeated 69 times Feb 12 21:23:33 vdev-3230 heartbeat: [6941]: WARN: Shutdown delayed until Communication is up. Feb 12 21:23:33 vdev-3230 heartbeat: [6941]: ERROR: Message hist queue is filling up (200 messages in queue) So - I understand that the 'message hist queue' filling up is a symptom unto itself to pursue (we have no packet filtering in place), but I'm confused by the behavior of heartbeat deciding to not shut down. In our case, this condition causes heartbeat to block forever. I've read this thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg01528.html and we don't have a mysterious 'OnlyForTesting' file manifesting. It looks like the code was added here: http://lists.community.tummy.com/pipermail/linux-ha-dev/2004-October/009212.html http://cvs.linux-ha.org/viewcvs/viewcvs.cgi/linux-ha/heartbeat/heartbeat.c?r1=1.322&r2=1.323 So - does a more recent release honor a 'shutdown dammit' option? -- Brian Reichert <[EMAIL PROTECTED]> 55 Crystal Ave. #286 Daytime number: (603) 434-6842 Derry NH 03038-1725 USA BSD admin/developer at large _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
