Hi Vlad,
No I haven't. 2.34 wasn't available when I had the problem. FYI I'm
still using glib-2.30.3 and I'll probably stay there until 3.34.0 is
stable or 2.32.4-r2 comes out :)
Pat.
On 05/11/2012 7:57 AM, Vladimir Elisseev wrote:
Patrick,
Gentoo devs suggested trying >=dev-libs/glib-2.
Patrick,
Gentoo devs suggested trying >=dev-libs/glib-2.34. Have you tried this
already?
Regards,
Vlad.
On Sun, 2012-11-04 at 08:45 -0800, Patrick Irvine wrote:
> Hey Guys,
>
> Just for the record, I just noticed this thread and it sounded familiar.
>I checked my gentoo systems and I had t
Pat,
Just in case, I've created a bug:
https://bugs.gentoo.org/show_bug.cgi?id=441730
Regards,
Vlad.
On Sun, 2012-11-04 at 08:45 -0800, Patrick Irvine wrote:
> Hey Guys,
>
> Just for the record, I just noticed this thread and it sounded familiar.
>I checked my gentoo systems and I had to m
Hey Guys,
Just for the record, I just noticed this thread and it sounded familiar.
I checked my gentoo systems and I had to mask glib-2.32.4-r1 and use
glib-2.30.3 in order to get corosync/pacemaker to work. I had the same
problem. Nodes couldn't talk to each other. Sorry I didn't notice
Thanks for the explanation. I saw coredumps in the directories you
mentioned already. The "suspicious -r1" includes two patches over
vanilla version of glib:
https://bugzilla.gnome.org/show_bug.cgi?id=679306
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-libs/glib/files/glib-2.32.4-CVE
03.11.2012 18:22, Vladimir Elisseev wrote:
> Vladislav,
>
> Thanks for the hint! Upgrading glig from 2.30.3 to 2.32.4 triggers this
> behavior of corosync. Do you know where I can find more info regarding
> this problem?
That is not corosync but pacemaker, which heavily uses glib internally.
And
Vladislav,
Thanks for the hint! Upgrading glig from 2.30.3 to 2.32.4 triggers this
behavior of corosync. Do you know where I can find more info regarding
this problem?
Vlad.
On Sat, 2012-11-03 at 16:22 +0300, Vladislav Bogdanov wrote:
> 03.11.2012 15:26, Vladimir Elisseev wrote:
> > I've been ab
Ups... It this a known fact? What is the base of your guess?
Regards,
Vlad.
On Sat, 2012-11-03 at 16:22 +0300, Vladislav Bogdanov wrote:
> 03.11.2012 15:26, Vladimir Elisseev wrote:
> > I've been able to reproduce the problem. Herewith I've attached
> > crm_report tarballs from both nodes. Althou
03.11.2012 15:26, Vladimir Elisseev wrote:
> I've been able to reproduce the problem. Herewith I've attached
> crm_report tarballs from both nodes. Although I don't know what
> particular package triggers this problem, but below is the list of what
> has been updated. Hopefully this helps.
I bet t
Yes, hb_report is there, thanks!
On Thu, 2012-11-01 at 11:40 +1100, Andrew Beekhof wrote:
> On Tue, Oct 30, 2012 at 4:35 PM, Vladimir Elisseev wrote:
> > Thanks for trying to help! Currently I can't provide crm_report from the
> > failed node, as I've decided to restore the complete node from bac
On Tue, Oct 30, 2012 at 4:35 PM, Vladimir Elisseev wrote:
> Thanks for trying to help! Currently I can't provide crm_report from the
> failed node, as I've decided to restore the complete node from backup.
> The versions I use are corosync-1.3.0 and pacemaker-1.0.10. Actually the
> problem occurre
Thanks for trying to help! Currently I can't provide crm_report from the
failed node, as I've decided to restore the complete node from backup.
The versions I use are corosync-1.3.0 and pacemaker-1.0.10. Actually the
problem occurred after updating quiet a few system packages, but all the
cluster r
On Sun, Oct 28, 2012 at 9:05 PM, Vladimir Elisseev wrote:
> Hello,
>
> I'm having problem that after reboot one cluster node can't join cluster
> anymore. Form the log file I can't understand what actually is going on.
> I only can see, that cib and crm both are respawned frequently. I'd
> appreci
Hello,
I'm having problem that after reboot one cluster node can't join cluster
anymore. Form the log file I can't understand what actually is going on.
I only can see, that cib and crm both are respawned frequently. I'd
appreciate any help. Below is relevant part of the log file:
Oct 28 10:52:22
14 matches
Mail list logo