Re: [ClusterLabs] Triggered assert at xml.c:594

2016-02-15 Thread Patrick Zwahlen
Thank you Lars. > -Original Message- > From: Lars Ellenberg [mailto:lars.ellenb...@linbit.com] > Sent: lundi, 15 février 2016 17:43 > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] Triggered assert at xml.c:594 > > On Sun, Feb 14, 2016 at 12:07:32PM +,

Re: [ClusterLabs] Triggered assert at xml.c:594

2016-02-15 Thread Lars Ellenberg
On Sun, Feb 14, 2016 at 12:07:32PM +, Patrick Zwahlen wrote: > Replying to myself, > > This seems to be related to the latest drbd RA (8.9.4+). > > Still, is it something we should worry about ? for the record, and as answered on DRBD-user as well: I suggest this is the fix for the "problem"

Re: [ClusterLabs] Triggered assert at xml.c:594

2016-02-14 Thread Patrick Zwahlen
-source clustering welcomed Subject: [ClusterLabs] Triggered assert at xml.c:594 Hi, Short: I'm getting asserts in my logs and wonder if I should worry. Long: I'm Running a lab on CentOS 7.2: pacemaker-1.1.13-10.el7.x86_64 corosync-2.3.4-7.el7_2.1.x86_64 Since my latest "yum upd

[ClusterLabs] Triggered assert at xml.c:594

2016-02-13 Thread Patrick Zwahlen
Hi, Short: I'm getting asserts in my logs and wonder if I should worry. Long: I'm Running a lab on CentOS 7.2: pacemaker-1.1.13-10.el7.x86_64 corosync-2.3.4-7.el7_2.1.x86_64 Since my latest "yum update", I see the following errors in my logs: Feb 13 15:22:54 san1.local crmd[1896]:error: