[ClusterLabs] pacemakerd quits after few seconds with some errors

[Gabriele Bulfon]

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 at 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 at 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 at 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 at 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 at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160823/97379995/attachment.htm>