Re: [ClusterLabs] issues with pacemaker daemonization

[ashutosh tiwari]

Thanks Ken.

Regards,
Ashutosh

On Fri, Nov 10, 2017 at 6:57 AM, <users-requ...@clusterlabs.org> wrote:

> Send Users mailing list submissions to
> users@clusterlabs.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.clusterlabs.org/mailman/listinfo/users
> or, via email, send a message with subject or body 'help' to
> users-requ...@clusterlabs.org
>
> You can reach the person managing the list at
> users-ow...@clusterlabs.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Users digest..."
>
>
> Today's Topics:
>
>1. Re: issues with pacemaker daemonization (Ken Gaillot)
>2. Re: Pacemaker 1.1.18 Release Candidate 4 (Ken Gaillot)
>3. Re: Issue in starting Pacemaker Virtual IP in RHEL 7 (Jan Pokorn?)
>4. Re: One cluster with two groups of nodes (Alberto Mijares)
>5. Pacemaker responsible of DRBD and a systemd resource
>   (Derek Wuelfrath)
>
>
> --
>
> Message: 1
> Date: Thu, 09 Nov 2017 09:49:20 -0600
> From: Ken Gaillot <kgail...@redhat.com>
> To: Cluster Labs - All topics related to open-source clustering
> welcomed<users@clusterlabs.org>
> Subject: Re: [ClusterLabs] issues with pacemaker daemonization
> Message-ID: <1510242560.5244.3.ca...@redhat.com>
> Content-Type: text/plain; charset="UTF-8"
>
> On Thu, 2017-11-09 at 15:59 +0530, ashutosh tiwari wrote:
> > Hi,
> >
> > We are observing that sometime pacemaker daemon gets the same
> > processgroup id as the process /script calling the "service pacemaker
> > start".?
> > While child processes of pacemaeker(cib/crmd/pengine) have there
> > processgroup id? same as there pid which is how things should be for
> > a daemon afaik.
> >
> > Do we expect it to be managed by init.d (centos 6) or pacemaker
> > binary.
> >
> > pacemaker version: pacemaker-1.1.14-8.el6_8.1.x86_64
> >
> >
> > Thanks and Regards,
> > Ashutosh Tiwari
>
> When pacemakerd spawns a child (cib etc.), it calls setsid() in the
> child to start a new session, which will set the process group ID and
> session ID to the child's PID.
>
> However it doesn't do anything similar for itself. Possibly it should.
> It's a longstanding to-do item to make pacemaker daemonize itself more
> "properly", but no one's had the time to address it.
> --
> Ken Gaillot <kgail...@redhat.com>
>
>
>
> --
>
> Message: 2
> Date: Thu, 09 Nov 2017 10:11:08 -0600
> From: Ken Gaillot <kgail...@redhat.com>
> To: Kristoffer Gr?nlund <kgronl...@suse.com>, Cluster   Labs - All
> topics related to open-source clustering welcomed
> <users@clusterlabs.org>
> Subject: Re: [ClusterLabs] Pacemaker 1.1.18 Release Candidate 4
> Message-ID: <1510243868.5244.5.ca...@redhat.com>
> Content-Type: text/plain; charset="UTF-8"
>
> On Fri, 2017-11-03 at 08:24 +0100, Kristoffer Gr?nlund wrote:
> > Ken Gaillot <kgail...@redhat.com> writes:
> >
> > > I decided to do another release candidate, because we had a large
> > > number of changes since rc3. The fourth release candidate for
> > > Pacemaker
> > > version 1.1.18 is now available at:
> > >
> > > https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1
> > > .18-
> > > rc4
> > >
> > > The big changes are numerous scalability improvements and bundle
> > > fixes.
> > > We're starting to test Pacemaker with as many as 1,500 bundles
> > > (Docker
> > > containers) running on 20 guest nodes running on three 56-core
> > > physical
> > > cluster nodes.
> >
> > Hi Ken,
> >
> > That's really cool. What's the size of the CIB with that kind of
> > configuration? I guess it would compress pretty well, but still.
>
> The test cluster is gone now, so not sure ... Beekhof might know.
>
> I know it's big enough that the transition graph could get too big to
> send via IPC, and we had to re-enable pengine's ability to write it to
> disk instead, and have the crmd read it from disk.
>
> >
> > Cheers,
> > Kristoffer
> >
> > >
> > > For details on the changes in this release, see the ChangeLog.
> > >
> > > This is likely to be the last release candidate before the final
> > > release next week. Any testing you can do is very welcome.
> --
> Ken Gaillot <kgail...@redha

Re: [ClusterLabs] issues with pacemaker daemonization

[Ken Gaillot]

On Thu, 2017-11-09 at 15:59 +0530, ashutosh tiwari wrote:
> Hi,
> 
> We are observing that sometime pacemaker daemon gets the same
> processgroup id as the process /script calling the "service pacemaker
> start". 
> While child processes of pacemaeker(cib/crmd/pengine) have there
> processgroup id  same as there pid which is how things should be for
> a daemon afaik.
> 
> Do we expect it to be managed by init.d (centos 6) or pacemaker
> binary.
> 
> pacemaker version: pacemaker-1.1.14-8.el6_8.1.x86_64
> 
> 
> Thanks and Regards,
> Ashutosh Tiwari

When pacemakerd spawns a child (cib etc.), it calls setsid() in the
child to start a new session, which will set the process group ID and
session ID to the child's PID.

However it doesn't do anything similar for itself. Possibly it should.
It's a longstanding to-do item to make pacemaker daemonize itself more
"properly", but no one's had the time to address it.
-- 
Ken Gaillot 

___
Users mailing list: Users@clusterlabs.org
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