[mysql*]
user root
group wheel
env.mysqlopts --defaults-extra-file=/root/.my.cnf
[exim_mailqueue]
group mail
[exim_mailstats]
group mail
[mailman]
user mailman
/etc/init.d/munin-node restart
su munin
crontab -e
remove the line, or just add an # to the beginning of it
*/5 * * * * /opt/munin/bin/munin-cron --force-root
Make sure that the password in /root/.my.cnf is valid, first.
Secondly, I have had this problem off and on for months with munin installs. To resolve it, this is what I did:
in /etc/munin/plugin-conf.d , you will see a file called cpanel.conf . Modify it completely to look like so:
then restart muninCode:[mysql*] user root group wheel env.mysqlopts --defaults-extra-file=/root/.my.cnf [exim_mailqueue] group mail [exim_mailstats] group mail [mailman] user mailman
This tells munin to pull the mysql environment from the file necessaryCode:/etc/init.d/munin-node restart
Of course , in this case you will need munin to run as ROOT. To do this:
su to your munin user
remove the munin crontabCode:su munin
then exit out of the shell, and add the SAME crontab (that was in the munin user) to root, adding --force-root to the end of the statement, so it'd be something like:Code:crontab -e remove the line, or just add an # to the beginning of it
Please note that this is NOT the exact entry, as I have my munin collection server on a non cp server, but this works for CP setups as wellCode:*/5 * * * * /opt/munin/bin/munin-cron --force-root
Good luck
env.mysqlopts --defaults-extra-file=/root/.my.cnf
No, I back it to the old.Did you add the --force-root option?
Either way, good to ehar it's working for you now.
Did you add the --force-root option?when I remove the munin crontab and add it to root crontab munin not work.
I confirm that upon adding "env.mysqlopts --defaults-extra-file=/root/.my.cnf" to "/etc/munin/plugin-conf.d/cpanel.conf" as shown above, then restarting munin-node, Munin began to display MySQL statistics without performing the other additional steps. To reiterate for other people, however, it will take time for the MySQL statistics data to accumulate.Make sure that the password in /root/.my.cnf is valid, first.
Secondly, I have had this problem off and on for months with munin installs. To resolve it, this is what I did:
in /etc/munin/plugin-conf.d , you will see a file called cpanel.conf . Modify it completely to look like so:
then restart muninCode:[mysql*] user root group wheel env.mysqlopts --defaults-extra-file=/root/.my.cnf [exim_mailqueue] group mail [exim_mailstats] group mail [mailman] user mailman
This tells munin to pull the mysql environment from the file necessaryCode:/etc/init.d/munin-node restart
Of course , in this case you will need munin to run as ROOT. To do this:
su to your munin user
remove the munin crontabCode:su munin
then exit out of the shell, and add the SAME crontab (that was in the munin user) to root, adding --force-root to the end of the statement, so it'd be something like:Code:crontab -e remove the line, or just add an # to the beginning of it
Please note that this is NOT the exact entry, as I have my munin collection server on a non cp server, but this works for CP setups as wellCode:*/5 * * * * /opt/munin/bin/munin-cron --force-root
Good luck
Thread starter | Similar threads | Forum | Replies | Date |
---|---|---|---|---|
H | Munin data from all servers shown on one server | Developer Experience | 0 | |
L | Munin Plugin - NTP kernel PLL estimated error | Developer Experience | 2 | |
P | change munin templates | Developer Experience | 1 | |
P | Munin and Perl 5.8.8 | Developer Experience | 1 | |
M | Munin Service Monitor - Page Not Found?? | Developer Experience | 8 |