- Original Message -
> From: "Kazunori INOUE"
> To: "The Pacemaker cluster resource manager"
> Sent: Friday, January 10, 2014 5:23:04 AM
> Subject: Re: [Pacemaker] lrmd segfault at pacemaker 1.1.11-rc1
>
> 2014/1/9 Andrew Beekhof :
> >
&
2014/1/9 Andrew Beekhof :
>
> On 8 Jan 2014, at 9:15 pm, Kazunori INOUE wrote:
>
>> 2014/1/8 Andrew Beekhof :
>>>
>>> On 18 Dec 2013, at 9:50 pm, Kazunori INOUE
>>> wrote:
>>>
Hi David,
2013/12/18 David Vossel :
>
> That's a really weird one... I don't see how it is possib
On 8 Jan 2014, at 9:15 pm, Kazunori INOUE wrote:
> 2014/1/8 Andrew Beekhof :
>>
>> On 18 Dec 2013, at 9:50 pm, Kazunori INOUE wrote:
>>
>>> Hi David,
>>>
>>> 2013/12/18 David Vossel :
That's a really weird one... I don't see how it is possible for op->id to
be NULL there.
2014/1/8 Andrew Beekhof :
>
> On 18 Dec 2013, at 9:50 pm, Kazunori INOUE wrote:
>
>> Hi David,
>>
>> 2013/12/18 David Vossel :
>>>
>>> That's a really weird one... I don't see how it is possible for op->id to
>>> be NULL there. You might need to give valgrind a shot to detect whatever
>>> is r
On 18 Dec 2013, at 9:50 pm, Kazunori INOUE wrote:
> Hi David,
>
> 2013/12/18 David Vossel :
>>
>> That's a really weird one... I don't see how it is possible for op->id to be
>> NULL there. You might need to give valgrind a shot to detect whatever is
>> really going on here.
>>
>> -- Voss
Hi David,
2013/12/18 David Vossel :
>
> That's a really weird one... I don't see how it is possible for op->id to be
> NULL there. You might need to give valgrind a shot to detect whatever is
> really going on here.
>
> -- Vossel
>
Thank you for advice. I try it.
Kazunori INOUE
_
- Original Message -
> From: "Kazunori INOUE"
> To: "pm"
> Sent: Tuesday, December 17, 2013 5:43:53 AM
> Subject: [Pacemaker] lrmd segfault at pacemaker 1.1.11-rc1
>
> Hi,
>
> When repeated 'node standby' and 'no
Hi,
When repeated 'node standby' and 'node online', lrmd crashed with
SIGSEGV because "op->id" in cancel_recurring_action() was NULL.
Dec 17 19:01:21 vm3 crmd[2433]: info: do_state_transition: State
transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS
cause=C_IPC_MESSAGE ori
Looks like a library versioning issue.
Try removing all the cluster packages and files and make sure only the
ubuntu packages are installed.
On Thu, Jan 5, 2012 at 6:23 AM, ruslan usifov wrote:
> Hello
>
> I install ubuntu package from this place (before that i install myself build
> packages):
>
Hello
I install ubuntu package from this place (before that i install myself
build packages):
https://launchpad.net/~ubuntu-ha-maintainers/+archive/ppa?field.series_filter=lucid
So yes.
2012/1/3 Andrew Beekhof
> On Thu, Dec 22, 2011 at 9:19 AM, ruslan usifov
> wrote:
> > Hello
> >
> > I upg
On Thu, Dec 22, 2011 at 9:19 AM, ruslan usifov wrote:
> Hello
>
> I upgraded cluster from pacemaker 1.0.11 to pacemaker 1.1.6, and some times
> on all nodes lrmd will segfault with follow backtrace
Thats strange, because the lrmd isnt part of the pacemaker package.
Did you upgrade cluster-glue to
Also some times backtrace look like this:
#0 0x7f2b3b9e0464 in __lll_lock_wait () from /lib/libpthread.so.0
#1 0x7f2b3b9db5d9 in _L_lock_953 () from /lib/libpthread.so.0
#2 0x7f2b3b9db3fb in pthread_mutex_lock () from /lib/libpthread.so.0
#3 0x7f2b3c2d3cf6 in g_main_context_fin
Hello
I upgraded cluster from pacemaker 1.0.11 to pacemaker 1.1.6, and some times
on all nodes lrmd will segfault with follow backtrace
#0 0xb77f3430 in __kernel_vsyscall ()
#1 0xb73e6af9 in __lll_lock_wait () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb73e213b in _L_lock_748 () from /lib/tl
13 matches
Mail list logo
