The Munin cPanel plugin feature displays a user the necessary information about CPU, Exim, Apache®, MySQL® usage, and other information with the help of rrdtool logging system. In case it fails to update the information, user should take it seriously as it is not working properly. In this document, we will discuss about the steps that will help in resolving such issue.
There are several ways of resolving the Munin update issue. They are:
The first thing that a user should do is, be confirm about the proper maintenance and running of the nightly cron, and see to it that whether crontab entry for Munin exists or not.
If so, then crontab -u munin -l command will return output resembling this example:
*/5 * * * * /usr/local/cpanel/3rdparty/perl/526/bin/munin-cron
Next thing that the user should do is, be confirm that whether munin:munin owns the files in the /var/lib/munin and /var/log/munin directories or not.
User has to run this following command in order to set the correct ownership:
chown -R munin:munin /var/log/munin
chown -R munin:munin /var/lib/munin
It is important to note for a user that in case the munin:munin does not own the files in the /var/log/munin directory, then the service will update the log files, but not the graphs that Munin will display.
User has to run the sudo -u munin munin-cron command in order to run the Munin manually.
Note that if a user have worked on this previous steps correctly, then the new entries will appear in the /var/log/munin/munin-update log file without any errors. If a user wants to update the daily graphs, he can refresh the Munin interface to get the updates.
It is to note that Munin’s weekly graphs display the updates after the time configured by the user in the crontab entry for Munin.
All information on how to resolve the Munin issue is outlined in this review.