Hello Dejan, On Wednesday, September 15, 2010, Dejan Muhamedagic wrote: > Hi, > > On Sat, Aug 28, 2010 at 04:21:31AM +0200, Tomasz Chmielewski wrote: > > Can I restrict logging to WARN and ERROR only? > > > > I have an enormous flood of "info" messages running through my syslog > > (for lrmd, crmd, attrd etc.) - is there a way to disable it and get only > > WARN and ERROR reported? > > syslog-ng should be able to filter out messages based on > severity. But I'd recommend against it. It'd be hard to support > the cluster without complete logs.
I see that as real problem as well. All those HA/pacemaker messages make it difficult to see other, non pacemaker/heartbeat/cluster-glue, failures in the logs. Most of those messages are IMHO also entirely useless for the admin, but seem to pacemaker debug messages. Now as you know, the good news it that I send list of patches this week to address at least the logging :) One of the patches allows to disable logd syslog logging at all. Logs go anyway to ha-log and ha-debug. And another patch makes filtering more easy, so it adds the common logd identifier to all syslog messages. That allows to greatly simplify syslog-ng rules. For example for DDN Lustre system I wrote a rule that writes a file "ha-log.useful". That file has mostly output from resource agents only (which other usually well hidden between all those pacemaker debug lines). Cheers, Bernd -- Bernd Schubert DataDirect Networks _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
