At 2017-02-15 23:13:08, "Christine Caulfield" <[email protected]> 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?
_______________________________________________
Users mailing list: [email protected]
http://lists.clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to