Pacemaker [SIGSEGV - Segmentation violation] using with Heartbeat 3.x

[Claudio]

According to:
http://oss.clusterlabs.org/pipermail/pacemaker/2013-November/020152.html

and my test case using:

Pacemaker - Version: 1.1.10+git20130802-1ubuntu2.3 - Architecture: armhf
Hearbeat - Version: 1:3.0.5-3.2 - Architecture: armhf
Cluster-Glue- Version: 1.0.11+hg2754-1.1build1 - Architecture: armhf

I got (into syslog):

 ccm: [4356]: info: Hostname:
 ccm: [4356]: info: Break tie for 2 nodes cluster
 ccm: [4356]: WARN: ccm_state_joined: received message with unknown cookie, just dropping
 ccm: [4356]: info: client (pid=4361) removed from ccm
 heartbeat: [4269]: WARN: Managed /usr/lib/heartbeat/crmd process 4361 killed by signal 11 [SIGSEGV - Segmentation violation].
 heartbeat: [4269]: ERROR: Client /usr/lib/heartbeat/crmd (pid=4361) killed by signal 11.
 heartbeat: [4269]: ERROR: Respawning client "/usr/lib/heartbeat/crmd":
 heartbeat: [4269]: info: Starting child client "/usr/lib/heartbeat/crmd" (109,114)
 heartbeat: [4427]: info: Starting "/usr/lib/heartbeat/crmd" as uid 109 gid 114 (pid 4427)
 heartbeat: [4269]: info: the send queue length from heartbeat to client crmd is set to 1024
 heartbeat: [4269]: info: killing /usr/lib/heartbeat/crmd process group 4427 with signal 15
 heartbeat: [4269]: info: Core process 4273 exited. 7 remaining
 heartbeat: [4269]: info: Core process 4274 exited. 6 remaining
 heartbeat: [4269]: info: Core process 4275 exited. 5 remaining
 heartbeat: [4269]: info: Core process 4276 exited. 4 remaining
 heartbeat: [4269]: info: Core process 4277 exited. 3 remaining
 heartbeat: [4269]: info: Core process 4278 exited. 2 remaining

then node always reboot by crmd after some time.
Using Heartbeat without Pacemaker (crm no into ha.cf) no problem occur.

Note that /usr/lib/heartbeat/crmd are soft links to:
lrwxrwxrwx 1 root root 18 Feb 5 19:51 /usr/lib/heartbeat/attrd -> ../pacemaker/attrd
lrwxrwxrwx 1 root root 16 Feb 5 19:51 /usr/lib/heartbeat/cib -> ../pacemaker/cib
lrwxrwxrwx 1 root root 17 Feb 5 19:51 /usr/lib/heartbeat/crmd -> ../pacemaker/crmd
lrwxrwxrwx 1 root root 20 Feb 5 19:51 /usr/lib/heartbeat/pengine -> ../pacemaker/pengine
lrwxrwxrwx 1 root root 21 Feb 5 19:51 /usr/lib/heartbeat/stonithd -> ../pacemaker/stonithd

[Claudio (kladiv)]

Releated to:

- https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/676391
- https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/1251298

Solve by now (until patched package)

- http://www.gossamer-threads.com/lists/linuxha/pacemaker/86023#86023

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Rafael David Tinoco (rafaeldtinoco)]

Thank you for taking the time to report this bug. In an effort to keep an
up-to-date and valid list of bugs to work on, I have reviewed this report
to verify it still requires effort and occurs on an Ubuntu release in
standard support, and it does not.

Judging by the existing comments, other related bugs and the pointed
upstream discussion thread, it appears that the wrong lrmd was being
set after upgrade and that led existing cluster to confusion when
connecting to the local resource manager daemon.

It is unfortunate that we were unable to resolve this defect, however
there appears to be no further action possible at this time. I am
therefore moving the bug to 'Incomplete'. If you disagree or have
new information, we would be grateful if you could please add a comment
stating why and then change the status of the bug to 'New'.