First disable
MySQL InnoDB free tablespace» critical alert
Munin service monitor can show a critical alert, «MySQL InnoDB free tablespace».
This warning should be disregarded.
The way to resolve this is to disable the InnoDB monitoring plugin. Remove the /etc/munin/plugins/mysql_innodbsymlink with the following:
rm -i /etc/munin/plugins/mysql_innodb
It will prompt you to remove the symlink, ensure that it mentions the file is a symbolic link:
# rm -i /etc/munin/plugins/mysql_innodb
rm: remove symbolic link ‘/etc/munin/plugins/mysql_innodb’? y
At that point, run the following commands to apply the new configuration:
(If you apply munin-cron without chown munin, it wont work)
systemctl restart munin-node chown munin:munin /etc/munin/munin.conf sudo -u munin /usr/local/cpanel/3rdparty/perl/532/bin/munin-cron
Second, Messages with the following characteristics are received every 5 minutes from Munin ([email protected])
Top stop it, modify /etc/munin/munin.conf
and add or modify this configuration
# Drop [email protected] and [email protected] an email everytime
# something changes (OK -> WARNING, CRITICAL -> OK, etc)
#contact.someuser.command mail -s "Munin notification" [email protected]
#contact.anotheruser.command mail -s "Munin notification" [email protected]
#
# For those with Nagios, the following might come in handy. In addition,
# the services must be defined in the Nagios server as well.
#contact.nagios.command /usr/bin/send_nsca nagios.host.comm -c /etc/nsca.conf
contacts me # may be unnecessary and cause warnings
contact.me.command mailx -r [email protected] -s "Munin notification ${var:host}" [email protected]
contact.me.always_send warning critical
contact.me.max_messages 20
# a simple host tree
[panelserver.mydomain.com]
address 127.0.0.1
use_node_name yes
notify_alias mydomain.comThen restart munin