[ClusterLabs] Possible idea for 2.0.0: renaming the Pacemaker daemons

Jehan-Guillaume de Rorthais jgdr at dalibo.com
Wed Mar 28 17:07:28 EDT 2018

On Wed, 28 Mar 2018 15:50:26 -0500
Ken Gaillot <kgaillot at redhat.com> wrote:
> > >  pacemakerd: PREFIX-launchd, PREFIX-launcher  
> > 
> > pacemakerd, alone, sounds perfectly fine to me.  
> Agreed -- but the argument against it is to allow something like "grep
> pcmk /var/log/messages" to get everything.

Then I would pick PREFIX-master... But then I would hate having a pcmk-master
process :(

Maybe all the logging information should be handled by one process so
syslog/journald/stderr are happy?

Despite it's multiprocess architecture, PostgreSQL either:

* emit to syslog/journald using the same ident for all process
* capture stderr of all process and redirect to one file.

> > >  cib: PREFIX-configd, PREFIX-state  
> > 
> > Tricky...It deals with both config and state...
> > 
> > By the way, why in the first place the CIB messages must be in the
> > log file?
> > Filling logs with XML diffs resulting from other actions already
> > logged earlier
> > sounds like duplicated informations.  
> They are kept out of the syslog, which is where most users are expected
> to look. They are in the detail log, which is for more advanced
> troubleshooting.

oh ok, sorry.

I just finished a day reading log file /var/log/pacemaker.log on a Suse 12 SP1
that was packed with XML diffs :/

Maybe I should have checked /var/log/messages or the syslog setup...

But honestly, I hate having mixed logs all packed in one same files
like /var/log/messages :/

> The detail log messages are useful mainly because CIB changes can come
> from external sources, not just cluster daemons,

Sure, but a simple info messages explaining that «the CIB has been updated by
tool "<tool_here>" » sound enough to me.

> and also to easily see the XML syntax was as expected.

And this can go to detail/debug logs I suppose.

More information about the Users mailing list