Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 288152 - sys-cluster/heartbeat fails to start with segmentation fault
Summary: sys-cluster/heartbeat fails to start with segmentation fault
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High major (vote)
Assignee: Gentoo Cluster Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-08 07:06 UTC by Ian Walker
Modified: 2011-10-18 17:32 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Walker 2009-10-08 07:06:42 UTC
sys-cluster/heartbeat-2.0.7-r2: segmentation fault when attempting to start heartbeat

Reproducible: Always

Steps to Reproduce:
1. /etc/init.d/heartbeat start

2. Error appears:

2009/10/08_08:57:38 INFO: IPadr Resource is stopped
2009/10/08_08:57:38 INFO: IPadr Resource is stopped
/etc/init.d/heartbeat: line 28: 18614 Segmentation fault /usr/lib/heartbeat/heartbeat &>/dev/null

3. When checking /var/log/messages:

segfault at 0 ip b7c1d168 sp bff77f5c error 4 in libc-2.9.so[b7bab000+13d000]
Actual Results:  
Service fails to start.

Expected Results:  
Service should start.

It used to work fine, and I only noticed when I restarted the server.  I wanted to emerge heartbeat-2.0.8 to see if this might help, but this doesn't work at all, and I can only emerge this version that I have installed.

I've also tried re-emerging heartbeat again and even glibc as well considering the error in /var/log/messages.

I'll happily add more info if you require it, just tell me what you need and I'll provide it.
Comment 1 VinnieNZ 2009-10-12 23:59:59 UTC
I am also experiencing this bug.  Happened after I upgraded Python from v2.4 to v2.6 and ran python-updater (which updated quite a few packages, and also included some that needed corresponding revdep-rebuilds run).

After this, heartbeat-2.0.7 and heartbeat-2.0.8 both SegFault.

This is on a x86 install (ie not 64bit).

Happy to also provide any info required in order to get this working again.
Comment 2 Ian Walker 2009-10-13 09:59:43 UTC
python-updater nor re-compiling glibc or heartbeat solved my problem, but the following did:

From an email from Kasper Kowalik, I am now running with heartbeat-2.0.8 without problems.

https://bugs.gentoo.org/show_bug.cgi?id=285305

patches applied to ebuild as per this aforementioned bug.  This is on an x86 install.
Comment 3 Kacper Kowalik (Xarthisius) (RETIRED) gentoo-dev 2011-10-18 17:32:35 UTC
+  18 Oct 2011; Kacper Kowalik <xarthisius@gentoo.org> -heartbeat-1.2.5.ebuild,
+  -heartbeat-1.2.5-r1.ebuild, -heartbeat-2.0.7-r2.ebuild,
+  -files/heartbeat-2.0.7-update-resources-failcount.patch,
+  -heartbeat-2.0.8.ebuild, -files/heartbeat-2.0.8-asneeded.patch,
+  -files/heartbeat-2.0.8-crm-assert.patch,
+  -files/heartbeat-2.0.8-crm-leaks.patch, -files/heartbeat-2.0.8-delay.patch,
+  -files/heartbeat-2.0.8-glibc.patch, -files/heartbeat-2.0.8-install_fix.patch,
+  -heartbeat-3.0.4-r1.ebuild:
+  Drop ancient and unusable versions of heartbeat-{1,2} since we have
+  heartbeat-3 stable