Re: [ClusterLabs] pacemakerd quits after few seconds with some errors
I found that pacemakerd leaves a core file where I launch it, nad here is the output from "mdb core": sonicle@xstorage1:/sonicle/etc/cluster/corosync# mdb core Loading modules: [ libc.so.1 ld.so.1 ] $C 08047a48 libqb.so.0.18.0`qb_thread_lock+0x16(0, feef9875, 8047a9c, fe9eb842, fe9ff000, 806fc78) 08047a68 libqb.so.0.18.0`qb_atomic_int_add+0x22(806fd84, 1, 8047a9c, 773) 08047a88 libqb.so.0.18.0`qb_ipcs_ref+0x23(806fc78, fea30960, feef9865, fe9de139, fede608f, 806fb58) 08047ab8 libqb.so.0.18.0`qb_ipcs_create+0x68(8057fd9, 0, 0, 8069470, 805302e, 20) 08047ae8 libcrmcommon.so.3.5.0`mainloop_add_ipc_server+0x77(8057fd9, 0, 8069470, 8047b64, 0, feffb0a8) 08047b28 main+0x18e(8047b1c, fef726a8, 8047b58, 8052d2f, 1, 8047b64) 08047b58 _start+0x83(1, 8047c70, 0, 8047c8c, 8047ca0, 8047cb4) Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon Da: Gabriele Bulfon A: kwenn...@redhat.com Cluster Labs - All topics related to open-source clustering welcomed Data: 23 agosto 2016 14.30.20 CEST Oggetto: Re: [ClusterLabs] pacemakerd quits after few seconds with some errors About the hacluster/haclient user/group, I staft to think that cib can't connect because it's started by pacemakerd with user hacluster, even though pacemakerd is started as root. Instead, just before pacemakerd is able to connect with the same call, but that is the root user. So I tried to run pacemakerd as hacluster, and infact it can't start that way. I tried then to add the uidgid spec in the corosync.conf, but seems not to work anyway. So ...should I start also corosync as hacluster? Is it safe to run everything as root? How can I force pacemakerd to run every child as root? ...if this is the problem... Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon -- Da: Klaus Wenninger A: users@clusterlabs.org Data: 23 agosto 2016 9.07.03 CEST Oggetto: Re: [ClusterLabs] pacemakerd quits after few seconds with some errors On 08/23/2016 08:50 AM, Gabriele Bulfon wrote: Ok, looks like Corosync now runs fine with its version, but then pacemakerd fails again with new errors on attrd and other daemons it tries to fork. The main reason seems around ha signon and cluster process group api. Any idea? Just to be sure: You recompiled pacemaker against your new corosync? Klaus Gabriele *Sonicle S.r.l. *: http://www.sonicle.com *Music: *http://www.gabrielebulfon.com *Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon -- Da: Jan Pokorný A: users@clusterlabs.org Data: 23 agosto 2016 7.59.37 CEST Oggetto: Re: [ClusterLabs] pacemakerd quits after few seconds with some errors On 23/08/16 07:23 +0200, Gabriele Bulfon wrote: Thanks! I am using Corosync 2.3.6 and Pacemaker 1.1.4 using the "--with-corosync". How is Corosync looking for his own version? The situation may be as easy as building corosync from GitHub-provided automatic tarball, which is never a good idea if upstream has its own way of proper release delivery: http://build.clusterlabs.org/corosync/releases/ (specific URLs are also being part of the corosync announcements on this list) The issue with automatic tarballs already reported: https://github.com/corosync/corosync/issues/116 -- Jan (Poki) ___ Users mailing list: Users@clusterlabs.org http://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 ___ Users mailing list: Users@clusterlabs.org http://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 ___ Users mailing list: Users@clusterlabs.org http://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 ___Users mailing list: Users@clusterlabs.orghttp://clusterlabs.org/mailman/listinfo/usersProject Home: http://www.clusterlabs.orgGetting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdfBugs: http://bugs.clusterlabs.org ___ Users mailing list: Users@
Re: [ClusterLabs] pacemakerd quits after few seconds with some errors
About the hacluster/haclient user/group, I staft to think that cib can't connect because it's started by pacemakerd with user hacluster, even though pacemakerd is started as root. Instead, just before pacemakerd is able to connect with the same call, but that is the root user. So I tried to run pacemakerd as hacluster, and infact it can't start that way. I tried then to add the uidgid spec in the corosync.conf, but seems not to work anyway. So ...should I start also corosync as hacluster? Is it safe to run everything as root? How can I force pacemakerd to run every child as root? ...if this is the problem... Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon -- Da: Klaus Wenninger A: users@clusterlabs.org Data: 23 agosto 2016 9.07.03 CEST Oggetto: Re: [ClusterLabs] pacemakerd quits after few seconds with some errors On 08/23/2016 08:50 AM, Gabriele Bulfon wrote: Ok, looks like Corosync now runs fine with its version, but then pacemakerd fails again with new errors on attrd and other daemons it tries to fork. The main reason seems around ha signon and cluster process group api. Any idea? Just to be sure: You recompiled pacemaker against your new corosync? Klaus Gabriele *Sonicle S.r.l. *: http://www.sonicle.com *Music: *http://www.gabrielebulfon.com *Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon -- Da: Jan Pokorný A: users@clusterlabs.org Data: 23 agosto 2016 7.59.37 CEST Oggetto: Re: [ClusterLabs] pacemakerd quits after few seconds with some errors On 23/08/16 07:23 +0200, Gabriele Bulfon wrote: Thanks! I am using Corosync 2.3.6 and Pacemaker 1.1.4 using the "--with-corosync". How is Corosync looking for his own version? The situation may be as easy as building corosync from GitHub-provided automatic tarball, which is never a good idea if upstream has its own way of proper release delivery: http://build.clusterlabs.org/corosync/releases/ (specific URLs are also being part of the corosync announcements on this list) The issue with automatic tarballs already reported: https://github.com/corosync/corosync/issues/116 -- Jan (Poki) ___ Users mailing list: Users@clusterlabs.org http://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 ___ Users mailing list: Users@clusterlabs.org http://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 ___ Users mailing list: Users@clusterlabs.org http://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 ___ Users mailing list: Users@clusterlabs.org http://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
Re: [ClusterLabs] pacemakerd quits after few seconds with some errors
Sure I did: created the new corosync package and installed on the dev machine before building and creating the new pacemaker package on the dev machine. Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon -- Da: Klaus Wenninger A: users@clusterlabs.org Data: 23 agosto 2016 9.07.03 CEST Oggetto: Re: [ClusterLabs] pacemakerd quits after few seconds with some errors On 08/23/2016 08:50 AM, Gabriele Bulfon wrote: Ok, looks like Corosync now runs fine with its version, but then pacemakerd fails again with new errors on attrd and other daemons it tries to fork. The main reason seems around ha signon and cluster process group api. Any idea? Just to be sure: You recompiled pacemaker against your new corosync? Klaus Gabriele *Sonicle S.r.l. *: http://www.sonicle.com *Music: *http://www.gabrielebulfon.com *Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon -- Da: Jan Pokorný A: users@clusterlabs.org Data: 23 agosto 2016 7.59.37 CEST Oggetto: Re: [ClusterLabs] pacemakerd quits after few seconds with some errors On 23/08/16 07:23 +0200, Gabriele Bulfon wrote: Thanks! I am using Corosync 2.3.6 and Pacemaker 1.1.4 using the "--with-corosync". How is Corosync looking for his own version? The situation may be as easy as building corosync from GitHub-provided automatic tarball, which is never a good idea if upstream has its own way of proper release delivery: http://build.clusterlabs.org/corosync/releases/ (specific URLs are also being part of the corosync announcements on this list) The issue with automatic tarballs already reported: https://github.com/corosync/corosync/issues/116 -- Jan (Poki) ___ Users mailing list: Users@clusterlabs.org http://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 ___ Users mailing list: Users@clusterlabs.org http://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 ___ Users mailing list: Users@clusterlabs.org http://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 ___ Users mailing list: Users@clusterlabs.org http://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
Re: [ClusterLabs] pacemakerd quits after few seconds with some errors
Ok, looks like Corosync now runs fine with its version, but then pacemakerd fails again with new errors on attrd and other daemons it tries to fork. The main reason seems around ha signon and cluster process group api. Any idea? Gabriele Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon -- Da: Jan Pokorný A: users@clusterlabs.org Data: 23 agosto 2016 7.59.37 CEST Oggetto: Re: [ClusterLabs] pacemakerd quits after few seconds with some errors On 23/08/16 07:23 +0200, Gabriele Bulfon wrote: Thanks! I am using Corosync 2.3.6 and Pacemaker 1.1.4 using the "--with-corosync". How is Corosync looking for his own version? The situation may be as easy as building corosync from GitHub-provided automatic tarball, which is never a good idea if upstream has its own way of proper release delivery: http://build.clusterlabs.org/corosync/releases/ (specific URLs are also being part of the corosync announcements on this list) The issue with automatic tarballs already reported: https://github.com/corosync/corosync/issues/116 -- Jan (Poki) ___ Users mailing list: Users@clusterlabs.org http://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 ___ Users mailing list: Users@clusterlabs.org http://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
Re: [ClusterLabs] pacemakerd quits after few seconds with some errors
On 23/08/16 07:23 +0200, Gabriele Bulfon wrote: > Thanks! I am using Corosync 2.3.6 and Pacemaker 1.1.4 using the > "--with-corosync". > How is Corosync looking for his own version? The situation may be as easy as building corosync from GitHub-provided automatic tarball, which is never a good idea if upstream has its own way of proper release delivery: http://build.clusterlabs.org/corosync/releases/ (specific URLs are also being part of the corosync announcements on this list) The issue with automatic tarballs already reported: https://github.com/corosync/corosync/issues/116 -- Jan (Poki) pgpQE2w5U4jgY.pgp Description: PGP signature ___ Users mailing list: Users@clusterlabs.org http://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
Re: [ClusterLabs] pacemakerd quits after few seconds with some errors
Thanks! I am using Corosync 2.3.6 and Pacemaker 1.1.4 using the
"--with-corosync".
How is Corosync looking for his own version?
Sonicle S.r.l.
:
http://www.sonicle.com
Music:
http://www.gabrielebulfon.com
Quantum Mechanics :
http://www.cdbaby.com/cd/gabrielebulfon
--
Da: Klaus Wenninger
A: users@clusterlabs.org
Data: 23 agosto 2016 4.54.44 CEST
Oggetto: Re: [ClusterLabs] pacemakerd quits after few seconds with some errors
On 08/23/2016 12:20 AM, Ken Gaillot wrote:
On 08/22/2016 12:17 PM, Gabriele Bulfon wrote:
Hi,
I built corosync/pacemaker for our XStreamOS/illumos : corosync starts
fine and log correctly, pacemakerd quits after some seconds with the
attached log.
Any idea where is the issue?
Pacemaker is not able to communicate with corosync for some reason.
Aug 22 19:13:02 [1324] xstorage1 corosync notice [MAIN ] Corosync
Cluster Engine ('UNKNOWN'): started and ready to provide service.
'UNKNOWN' should show the corosync version. I'm wondering if maybe you
have an older corosync without configuring the pacemaker plugin. It
would be much better to use corosync 2 instead, if you can.
If corosync is not able to determine its' own version the
pacemaker-build might not have been able as well. So it
might have made some weird decisions/assumptions ...
like e.g. not building the plugin at all ... assuming you
are not using corosync 2+ ...
Thanks,
Gabriele
*Sonicle S.r.l. *: http://www.sonicle.com
*Music: *http://www.gabrielebulfon.com
*Quantum Mechanics : *http://www.cdbaby.com/cd/gabrielebulfon
___
Users mailing list: Users@clusterlabs.org
http://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
___
Users mailing list: Users@clusterlabs.org
http://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
___
Users mailing list: Users@clusterlabs.org
http://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
Re: [ClusterLabs] pacemakerd quits after few seconds with some errors
On 08/23/2016 12:20 AM, Ken Gaillot wrote:
> On 08/22/2016 12:17 PM, Gabriele Bulfon wrote:
>> Hi,
>>
>> I built corosync/pacemaker for our XStreamOS/illumos : corosync starts
>> fine and log correctly, pacemakerd quits after some seconds with the
>> attached log.
>> Any idea where is the issue?
> Pacemaker is not able to communicate with corosync for some reason.
>
> Aug 22 19:13:02 [1324] xstorage1 corosync notice [MAIN ] Corosync
> Cluster Engine ('UNKNOWN'): started and ready to provide service.
>
> 'UNKNOWN' should show the corosync version. I'm wondering if maybe you
> have an older corosync without configuring the pacemaker plugin. It
> would be much better to use corosync 2 instead, if you can.
If corosync is not able to determine its' own version the
pacemaker-build might not have been able as well. So it
might have made some weird decisions/assumptions ...
like e.g. not building the plugin at all ... assuming you
are not using corosync 2+ ...
>
>> Thanks,
>> Gabriele
>>
>>
>> *Sonicle S.r.l. *: http://www.sonicle.com
Re: [ClusterLabs] pacemakerd quits after few seconds with some errors
On 08/22/2016 12:17 PM, Gabriele Bulfon wrote:
> Hi,
>
> I built corosync/pacemaker for our XStreamOS/illumos : corosync starts
> fine and log correctly, pacemakerd quits after some seconds with the
> attached log.
> Any idea where is the issue?
Pacemaker is not able to communicate with corosync for some reason.
Aug 22 19:13:02 [1324] xstorage1 corosync notice [MAIN ] Corosync
Cluster Engine ('UNKNOWN'): started and ready to provide service.
'UNKNOWN' should show the corosync version. I'm wondering if maybe you
have an older corosync without configuring the pacemaker plugin. It
would be much better to use corosync 2 instead, if you can.
>
> Thanks,
> Gabriele
>
>
> *Sonicle S.r.l. *: http://www.sonicle.com
[ClusterLabs] pacemakerd quits after few seconds with some errors
Hi, I built corosync/pacemaker for our XStreamOS/illumos : corosync starts fine and log correctly, pacemakerd quits after some seconds with the attached log. Any idea where is the issue? Thanks, Gabriele Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon corosync.log Description: binary/octet-stream ___ Users mailing list: Users@clusterlabs.org http://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
