[Pacemaker] logd and corosync/pacemaker

Dejan Muhamedagic dejanmm at fastmail.fm
Fri Mar 19 10:54:52 UTC 2010


Hi,

On Fri, Mar 19, 2010 at 10:34:27AM +0100, Andreas Mock wrote:
> -----Ursprüngliche Nachricht-----
> Von: Dejan Muhamedagic <dejanmm at fastmail.fm>
> Gesendet: 15.03.2010 11:01:03
> An: pacemaker at oss.clusterlabs.org
> Betreff: Re: [Pacemaker] logd and corosync/pacemaker
> 
> >Hi,
> >
> >On Fri, Mar 12, 2010 at 05:24:53PM +0100, Andreas Mock wrote:
> >> Hi all,
> >> 
> >> with heartbeat it was adviced to use logd for logging.
> >> 
> >> a) Is still valid for a corosync/pacemaker combination?
> >
> >Yes.
> >
> >> b) If yes, how is it enabled?
> >
> >Set use_logd to yes in the pacemaker service stanza in
> >corosync.conf.
> 
> 
> Hi Dejan,
> 
> I don't get it work with corosync. Probably some insight is missing.
> a) Can you give me an example of that stanza?

service {
        #Default to start mgmtd with pacemaker
        use_mgmtd:      yes
        #Use logd for pacemaker
        use_logd:       yes
        #Version
        ver:    0
        #The name of the service
        name:   pacemaker
}

> b) Which services start to log to logd if logd is enabled?

All pacemaker subsystems.

> c) Does corosync also log to logd? 

No.

> d) If I enable logd, what does the paragraph
> logging {
>  fileline: off
>  to_syslog: no
>  to_stderr: no
>  to_logfile: yes
>  syslog_facility: daemon
>  logfile: /tmp/corosync.log
>  debug: on
>  timestamp: on
>  logger_subsys {
>  subsys: AMF
>  debug: off
>  }
> }
> in /etc/corosync/corosync.conf mean?

That's for corosync.

Thanks,

Dejan

> Help needed.   :-)
> 
> Thank you in advance
> Andreas
> 
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker




More information about the Pacemaker mailing list