[ClusterLabs] corosync dead loop in segfault handler
Christine Caulfield
ccaulfie at redhat.com
Thu Feb 16 06:38:03 EST 2017
On 16/02/17 09:31, cys wrote:
> The attachment includes coredump and logs just before corosync went wrong.
>
> The packages we use:
> corosync-2.3.4-7.el7_2.1.x86_64
> corosynclib-2.3.4-7.el7_2.1.x86_64
> libqb-0.17.1-2.el7.1.x86_64
>
> But they are not available any more at mirror.centos.org. If you can't find them anywhere, I can send you the RPMs.
> The debuginfo packages can be downloaded from http://debuginfo.centos.org/7/x86_64/.
>
Can you send me the RPMs please? I tried the RHEL ones with the same
version number but they don't work (it was worth a try!)
Thanks
Chrissie
> Unfortunately corosync was restarted yesterday, and I can't get the blackbox dump covering the day the incident occurred.
>
> At 2017-02-16 16:00:05, "Christine Caulfield" <ccaulfie at redhat.com> wrote:
>> On 16/02/17 03:51, cys wrote:
>>> At 2017-02-15 23:13:08, "Christine Caulfield" <ccaulfie at redhat.com> wrote:
>>>>
>>>> Yes, it seems that some corosync SEGVs trigger this obscure bug in
>>>> libqb. I've chased a few possible causes and none have been fruitful.
>>>>
>>>> If you get this then corosync has crashed, and this other bug is masking
>>>> the actual diagnostics - I know, helpful :/
>>>>
>>>> It's on my list
>>>>
>>>> Chrissie
>>>>
>>>
>>> Thanks.
>>> I think you have noticed that my_service_list[3] is invalid.
>>> About the SEGV, do you need additional information? coredump or logs?
>>>
>>
>> A blackbox dump and (if possible) coredump would be very useful if you
>> can get them. thank you.
>>
>> Chrissie
More information about the Users
mailing list