[Pacemaker] syslog_priority ignored?
Dejan Muhamedagic
dejanmm at fastmail.fm
Thu Dec 30 18:07:24 UTC 2010
Hi,
On Thu, Dec 30, 2010 at 09:18:07AM +0100, Martin Spuetz wrote:
> Hi,
>
> On 28.12.2010 18:04, Dejan Muhamedagic wrote:
> > On Tue, Dec 28, 2010 at 02:29:22PM +0100, Martin Spuetz wrote:
> >> Hello,
> >>
> >> I don't know how to disable the flooding of syslog with messages of the
> >> various daemons.
> >>
> >> I only want warnings and errors in syslog.
> >
> > Not a good idea. Your logs won't be useful in case you run into
> > problems. Why don't you use a separate syslog_facility such as
> > local6 and then redirect all pacemaker/corosync messages to a
> > separate log file?
>
> I tried that but I still have messages in /var/log/messages, at least
> messages from cibadmin (afaik).
Right. That's due to cibadmin (and other command line tools) not
being started by corosync/heartbeat and therefore don't know
about the logging configuration.
> syslog.conf:
> > *.info;mail.none;news.none;authpriv.none;cron.none;local6.none /var/log/messages
> > # corosync
> > local6.* /var/log/corosync.log
>
> corosync.conf:
> > logging {
> > fileline: off
> > to_stderr: no
> > to_logfile: no
> > to_syslog: yes
> > syslog_facility: local6
> > debug: off
> > timestamp: off
> > }
>
> After I executed "crm configure show", in /var/log/messages:
>
> > Dec 30 09:12:31 middleware-a cibadmin: [8060]: info: Invoked: cibadmin -Ql
>
> Bug or feature?
Somewhere in between ;-)
Not sure if/how that can be fixed, but you can open a bugzilla
and we'll see.
Thanks,
Dejan
> Greetings
> Martin
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
More information about the Pacemaker
mailing list