Summary: | sys-cluster/heartbeat fails to start with segmentation fault | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ian Walker <scatmanwalks> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Cluster Team <cluster> |
Status: | RESOLVED WONTFIX | ||
Severity: | major | CC: | spamtrap+gentoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ian Walker
2009-10-08 07:06:42 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. 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. + 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 |