Stop Munin messages from /var/log/syslog

loggingmuninsyslog

I am using munin on a system which is adding a log entry in syslog everytime the munin-node cron job executes. It is not an issue but it sometimes makes other errors spotting difficult. There are entries like

Feb 28 07:05:01 li235-57 CRON[2634]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi)

every 5 minutes and I was wondering how can I stop the messages going into syslog. For munin specific errors I anyways have to keep an eye on /var/log/munin/*

Thanks
Sparsh

Best Answer

Depends on syslog. If use rsyslog(Ubuntu/Debian), you can edit /etc/rsyslog.d/50-default.conf:

#
# First some standard log files.  Log by facility.
#
:msg,contains,"/etc/munin/plugins/apt_all update 7200" ~
auth,authpriv.*                 /var/log/auth.log

It's a cron syslog message(not Munin).

Related Solutions

Add a local application to syslog excluded from /var/log/messages

Try replacing

*.info;mail.none;authpriv.none;cron.none                /var/log/messages

*.info;mail.none;authpriv.none;cron.none;local1.!=info                /var/log/messages

This will log message that match : any facility with level info AND facility not mail AND facility not authpriv AND facility local1 execpt when level is info.

Linux – logrotate does not compress /var/log/messages

Adding delaycompress to the configuration section for /var/log/messages solved the problem.

From man logrotate:

   delaycompress
          Postpone  compression of the previous log file to the next rota‐
          tion cycle.  This only has effect when used in combination  with
          compress.   It  can  be used when some program cannot be told to
          close its logfile and thus might continue writing to the  previ‐
          ous log file for some time.

I guess sysklogd, my syslog daemon, cannot be told to close its logfile, and thus this is necessary.

Interestingly, the original configuration I had (without the delaycompress directive), came straight out of man logrotate (except I changed weekly to daily):

   # sample logrotate configuration file
   compress

   /var/log/messages {
       rotate 5
       weekly
       postrotate
           /usr/bin/killall -HUP syslogd
       endscript
   }

Best Answer

Related Solutions

Add a local application to syslog excluded from /var/log/messages

Linux – logrotate does not compress /var/log/messages

Related Topic