Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 441730 - =sys-cluster/pacemaker-1.0.10 crashes with =dev-libs/glib-2.32.4-r1
Summary: =sys-cluster/pacemaker-1.0.10 crashes with =dev-libs/glib-2.32.4-r1
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Cluster Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-04 11:21 UTC by Vlad
Modified: 2013-04-18 09:53 UTC (History)
1 user (show)

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


Attachments
hb_report form node1 (srv1.tar.bz2,67.46 KB, application/octet-stream)
2012-11-04 14:25 UTC, Vlad
Details
hb_report from node2 (srv2.tar.bz2,67.66 KB, application/octet-stream)
2012-11-04 14:26 UTC, Vlad
Details
emerge --info (emerge-info.txt,16.08 KB, text/plain)
2012-11-04 14:26 UTC, Vlad
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vlad 2012-11-04 11:21:42 UTC
Latest stable glib can't be used with latest stable pacemaker. With glib-2.30.3 everything works as expected.

Reproducible: Always

Steps to Reproduce:
1. Install latest stable pacemaker, glib, corosync
2. start corosync
Comment 1 Samuli Suominen (RETIRED) gentoo-dev 2012-11-04 11:33:19 UTC
Just making sure: Did you remember to recompile dbus-glib after glib upgrade? As noted by the message at the end of glib upgrade. Needs to be done everytime.
Comment 2 Vlad 2012-11-04 14:00:13 UTC
(In reply to comment #1)
> Just making sure: Did you remember to recompile dbus-glib after glib
> upgrade? As noted by the message at the end of glib upgrade. Needs to be
> done everytime.

I don't have dbus-glib installed, so I even haven't seen this warning (it appears only if "has_version dev-libs/dbus-glib").
Comment 3 Samuli Suominen (RETIRED) gentoo-dev 2012-11-04 14:20:08 UTC
emerge --info output, console output when running pacemaker, and with relavent GLib debug flags enabled. moving to maintainers.
Comment 4 Vlad 2012-11-04 14:25:35 UTC
Created attachment 328324 [details]
hb_report form node1
Comment 5 Vlad 2012-11-04 14:26:01 UTC
Created attachment 328326 [details]
hb_report from node2
Comment 6 Vlad 2012-11-04 14:26:24 UTC
Created attachment 328328 [details]
emerge --info
Comment 7 Vlad 2012-11-04 14:29:09 UTC
(In reply to comment #3)
> emerge --info output, console output when running pacemaker, and with
> relavent GLib debug flags enabled. moving to maintainers.

I've attached corresponding data, however instead of console output there's hb_report's from both nodes for the time of pacemaker crash (as it was recommended in the clusterlabs mailing list)
Comment 8 Samuli Suominen (RETIRED) gentoo-dev 2012-11-05 10:25:39 UTC
reopening since the requested data has been provided. 

please try with >=dev-libs/glib-2.34 too to see if this has been fixed already.
Comment 9 Pacho Ramos gentoo-dev 2012-11-07 18:59:43 UTC
Before that (glib-2.34 is hardmasked I think), please test with pacemaker-1.1.7
Comment 10 Vlad 2013-04-13 10:57:40 UTC
(In reply to comment #9)
> Before that (glib-2.34 is hardmasked I think), please test with
> pacemaker-1.1.7

pacemaker-1.1.7 has a _LOT_ of changes.... Nevertheless finally I had some time for tests and combination of:
dev-libs/glib-2.34.3
sys-cluster/cluster-glue-1.0.11
sys-cluster/pacemaker-1.0.10

seems to work fine (as least so far).
Comment 11 Ultrabug gentoo-dev 2013-04-18 09:53:49 UTC
I'm sorry Vlad, thanks for your time on this matter.

+  18 Apr 2013; Ultrabug <ultrabug@gentoo.org> pacemaker-1.0.10.ebuild,
+  pacemaker-1.0.12.ebuild:
+  add blockers for glib-2.32* on pacemaker-1.0.x wrt #441730
+

BTW, I'm inclined to drop <pacemaker-1.1.x since we can't keep up with such versions unsupported by upstream.

Meanwhile, I hope this will help.