Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux-HA: Users

how do I cut down the amount of logging?

 

 

Linux-HA users RSS feed   Index | Next | Previous | View Threaded


mangoo at wpkg

Aug 27, 2010, 7:21 PM

Post #1 of 4 (368 views)
Permalink
how do I cut down the amount of logging?

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?


--
Tomasz Chmielewski
http://wpkg.org


_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems


dejanmm at fastmail

Sep 15, 2010, 9:08 AM

Post #2 of 4 (299 views)
Permalink
Re: how do I cut down the amount of logging? [In reply to]

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.

Thanks,

Dejan

>
> --
> Tomasz Chmielewski
> http://wpkg.org
>
>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems


bs_lists at aakef

Sep 17, 2010, 8:20 AM

Post #3 of 4 (290 views)
Permalink
Re: how do I cut down the amount of logging? [In reply to]

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
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems


dejanmm at fastmail

Sep 22, 2010, 4:24 AM

Post #4 of 4 (273 views)
Permalink
Re: how do I cut down the amount of logging? [In reply to]

Hi Bernd,

On Fri, Sep 17, 2010 at 05:20:18PM +0200, Bernd Schubert wrote:
> 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.

I also don't like mixing the pacemaker logs with system logs.
What's wrong with using a facility such as local7 for the HA
logs? Otherwise, yes, I understand your pain.

> 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).

Did you check the load of syslog-ng in this case?

Cheers,

Dejan

> Cheers,
> Bernd
>
> --
> Bernd Schubert
> DataDirect Networks
> _______________________________________________
> Linux-HA mailing list
> Linux-HA [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Linux-HA users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.