About two month ago, dealing with a bug report of some paying customer, I fixed some long standing bugs in the heartbeat communication layer that caused heartbeat to segfault, and other bad behaviour.
These bugs where triggered by "misbehaving" API clients, respectively massive packet loss on the communication links, and have been present basically since inception. The changelog does not really look spectacular, but is supposed to very much improve the robustness of the heartbeat communication stack if you experience massive packet loss on all channels, for whatever reason. As these are fixes that affect the heartbeat messaging core, they are relevant for both Pacemaker and "haresources" style clusters. Changelog: - do not request retransmission of lost messages from dead members - fix segfault due to recursion in api_remove_client_pid - properly cleanup pending delayed rexmit requests before reset of seqtrack - create HA_RSCTMP on start, if necessary - improve detection of pacemaker clusters in init script Tarball: http://hg.linux-ha.org/heartbeat-STABLE_3_0/archive/STABLE-3.0.5.tar.bz2 Enjoy! -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com _______________________________________________________ Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/