Planned for 11.34 Rotation for Large Munin log files [Case 37444]

[fuzioneer]

My /var/log/munin folder files are getting quite large and wandered is there a setting somewhere i have missed to delete old data or a log rotation etc

-rw-r--r-- 1 munin munin 465M Jan 21 19:55 munin-graph.log
-rw-r--r-- 1 munin munin 364M Jan 21 19:55 munin-html.log
-rw-r--r-- 1 munin munin 63M Jan 21 19:55 munin-limits.log
-rw-r--r-- 1 root wheel 77M Jan 21 19:55 munin-node.log
-rw-r--r-- 1 munin munin 1.3G Jan 21 19:55 munin-update.log

[lbeachmike]

Does anybody have an answer to this?

My munin-update.log file is 1.7 gig -


[root@host munin]# du -sh *
583M munin-graph.log
456M munin-html.log
77M munin-limits.log
91M munin-node.log
1.7G munin-update.log

[lbeachmike]

After contacting cpanel support, I've cleared the munin-update.log file manually.

These logs should be included in cpanel's log rotation functionality. Please add this functionality.

Thanks.

Mike

[chican0]

How did you clear the log? What command did you use?

[lbeachmike]

I do not fully recall the details on this, but I actually think that we simply deleted the log files with no impact to munin.

Take a look at their content. I believe that the details are not anything important. However, you can simply backup the files and move them to a directory in a partition where you have more space.

Then run Munin and I believe it will simply start a new log file with no adverse impact.

For future, you could make a symbolic link using ln command, which points to another directory in a partition where you have more space.

Hope that helps.

Mike

[postcd]

Please can anyone describe how to put this /var/log/munin/munin-update.log into rotation (periodically clear it) if its proper way?

pico /etc/logrotate.conf

[cPanelDavidG]

I spoke with a developer about this. The Munin log files are stored in /var/log which is managed/rotated by the operating system, hence we do not rotate any logs there. The logs that cPanel rotates are those outside /var/log such as those in /usr/local/cpanel/logs/ and thus not managed by your OS.

Essentially, we'd need to move the Munin log file (a customization to the Munin software, which would noticeably slow deployment of new versions of Munin) to avoid any conflicts with the OS.

[ethix]

This what I did hope it helps someone.

Create a file called munin in

/etc/logrotate.d

and place the bellow in it (change the options to what you want).

/var/log/munin/*log {
    weekly
    size 50M
    rotate 5
    compress
    missingok
    notifempty
    sharedscripts
    postrotate
         /sbin/service munin-node restart > /dev/null 2>/dev/null || true
    endscript
}

Some servers are already rotating the munin logs...?

[DomineauX]

As Munin is installed by cPanel as a plugin, have the plugin add a logrotate.d rule seems reasonable.

[SageBrian]

This what I did hope it helps someone.

Create a file called munin in

/etc/logrotate.d

and place the bellow in it

very helpful. Thank you.

[cPanelDavidG]

I spoke to our Product Manager about adding Munin logs to logroate.d by default - turns out we've already got a case on it but it's been sitting idle for a while. I added some new information to our internal case to get things moving along .

[webmastergreg]

Create a file called munin in

/etc/logrotate.d

and place the bellow in it

very helpful. Thank you.

Yes for me too, but since applied, shouldn't we see the file next to the others in the log rotation list ?

[Joriz]

Thank you ethix!

Hope this solves my big munin-update.log problem

[cPanelDavidG]

Update: This is currently being targeted for version 11.34.

[johnburk]

Great! Will 11.34 also include munin 1.47 or perhaps 2.0 will be released by then?