MUNIN Plugin WARN: MySQL InnoDB free tablespace

[Slatko]

Hello i installed yesteday the Munin Plugin.
It works great :D
But it shows me: MySQL InnoDB free tablespace WARN
Here is the Picture:


What it means?

 

[Defected]

I see the same weird behavior in a couple of servers and also on fresh installed machines. In an older ticket i've opened about this, support said that it's probably a munin bug. They were able to reproduce this behavior.

[email protected] [/etc/munin/plugins]# ./mysql_innodb
ERROR 1045 (28000): Access denied for user 'munin'@'localhost' (using password: YES)

I think there is a case opened (case 48107), so a fix might be released. Keep an eye on the changelog.

 

[SoftDux]

Does anyone know what causes this error, and how to fix it?

Is it an actual problem with the DB?

 

[fijumen]

Happened to me too, on a 2 new servers, must be a Munin bug, hope someone will update this thread after bug fix.

 

[cPanelTristan]

This warning should be disregarded. It is due to how Munin versus MySQL handle tablespace for InnoDB. By default, Munin throws a warning at 2GB free tablespace and critical alert at 1GB free tablespace. However, MySQL defaults to creating a 10MB autoexpanding tablespace. The tablespace can be verified with:

mysql -e "SHOW VARIABLES LIKE 'innodb_data_file_path'"

This means InnoDB will perpetually show <10MB of space (resulting in a permanent Munin warning) yet will always seamlessly autoextend as needed. The only "limit" in such a configuration is the partition that /var/lib/mysql is stored on. This render's the InnoDB free tablespace useless in an "autoextend" configuration.

The way to resolve is simply to disable the alerts. Create this file:

vi /etc/munin/plugin-conf.d/mysql_innodb

Place the following inside the file:

[mysql_innodb]
env.warning 0
env.critical 0

At that point, run the following commands:

/etc/init.d/munin-node restart
su munin -c /usr/bin/munin-cron

 

[alphawolf50]

Also, if you use innodb_file_per_table, there is no point even running this plugin. It is safe to:

# rm /etc/munin/plugins/mysql_innodb

This doesn't delete the actual plugin, only the symlink to the plugin. The actual plugin resides at:

/usr/share/munin/plugins/mysql_innodb.

Do not delete that one.

EDIT: after you've deleted the plugin, make sure you # service munin-node restart

 

[opentoe]

This Munin "bug" is from 2011, and is still happening today in 2013?

 

[Astral God]

This is not a bug, but a "bad" default configuration of Munin; please read posts #6 and #7.

 

[kamm]

I just installed munin using WHM > Manage Plugins. After the install I noticed the "MySQL InnoDB free tablespace" warning and have followed cPanelTristan's instructions in post #5.

Those commands ran OK until the last one...
su munin -c /usr/bin/munin-cron
which returns...
This account is currently not available.

Munin seems to be running OK and the warning has gone, but what about that last command? Perhaps something's changed since this post was written?

 

[Daky]

I am getting the same message.

Stopping Munin Node agents: [ OK ]
Starting Munin Node: [ OK ]
[email protected]*** [~]# su munin -c /usr/bin/munin-cron
This account is currently not available.

Please advise

 

[musioc]

Hello
Same error :
[email protected] [~]# su munin
This account is currently not available.

 

[cPanelMichael]

Hello

You can run the following commands instead:

su - munin --shell=/bin/bash
/usr/local/cpanel/3rdparty/perl/514/bin/munin-cron

Thank you.

 

[mahesh123]

hello

showing same warning ...


Thank you ..

 

[cPanelMichael]

showing same warning ...

Have you tried any of the solutions provided in this thread?

Thanks.

 

[RobinF28]

Hi,

This worked for me, thanks.

No more warnings showing at the MUNIN graph InnoDB free.

To help anyone wondering about the command flow, my terminal screen was something like this, FYI:

[email protected] [~]# mysql -e "SHOW VARIABLES LIKE 'innodb_data_file_path'"
+-----------------------+------------------------+
| Variable_name | Value |
+-----------------------+------------------------+
| innodb_data_file_path | ibdata1:10M:autoextend |
+-----------------------+------------------------+

[email protected] [~]# vi /etc/munin/plugin-conf.d/mysql_innodb

[email protected] [~]# cat /etc/munin/plugin-conf.d/mysql_innodb
[mysql_innodb]
env.warning 0
env.critical 0

[email protected] [~]# /etc/init.d/munin-node restart
Stopping Munin Node agents: [ OK ]
Starting Munin Node: [ OK ]

[email protected] [~]# su munin -c /usr/bin/munin-cron
This account is currently not available.

[email protected] [~]# su - munin --shell=/bin/bash
Attempting to create directory /home/munin/perl5
[email protected] [~]# /usr/local/cpanel/3rdparty/bin/munin-cron
[email protected] [~]#

[email protected] [~]# logout
[email protected] [~]#

 

[cPanelMichael]

I am happy to see you were able to address the issue. Thank you for updating us with the outcome.

 

[jmcguirl]

Hi,

This worked for me, thanks.

No more warnings showing at the MUNIN graph InnoDB free.

To help anyone wondering about the command flow, my terminal screen was something like this, FYI:

[email protected] [~]# mysql -e "SHOW VARIABLES LIKE 'innodb_data_file_path'"
+-----------------------+------------------------+
| Variable_name | Value |
+-----------------------+------------------------+
| innodb_data_file_path | ibdata1:10M:autoextend |
+-----------------------+------------------------+

[email protected] [~]# vi /etc/munin/plugin-conf.d/mysql_innodb

[email protected] [~]# cat /etc/munin/plugin-conf.d/mysql_innodb
[mysql_innodb]
env.warning 0
env.critical 0

[email protected] [~]# /etc/init.d/munin-node restart
Stopping Munin Node agents: [ OK ]
Starting Munin Node: [ OK ]

[email protected] [~]# su munin -c /usr/bin/munin-cron
This account is currently not available.

[email protected] [~]# su - munin --shell=/bin/bash
Attempting to create directory /home/munin/perl5
[email protected] [~]# /usr/local/cpanel/3rdparty/perl/514/bin/munin-cron
[email protected] [~]#

[email protected] [~]# logout
[email protected] [~]#

As this port gets older, the very last munin command should be changed to:

/usr/local/cpanel/3rdparty/bin/munin-cron

It is a symlink that always points to the latest version of munin-cron. Just my two cents.

 

[kitchin]

As this port gets older, the very last munin command should be changed to:

/usr/local/cpanel/3rdparty/bin/munin-cron

It is a symlink that always points to the latest version of munin-cron. Just my two cents.

No symlink here. Just look for the latest perl in
/usr/local/cpanel/3rdparty/perl