The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

MUNIN Plugin WARN: MySQL InnoDB free tablespace

Discussion in 'Database Discussions' started by Slatko, May 9, 2011.

  1. Slatko

    Slatko Member

    Joined:
    Jan 21, 2011
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    1
    Hello i installed yesteday the Munin Plugin.
    It works great :D
    But it shows me: MySQL InnoDB free tablespace WARN :eek:
    Here is the Picture:


    What it means?
     

    Attached Files:

  2. Defected

    Defected Member

    Joined:
    Dec 14, 2009
    Messages:
    17
    Likes Received:
    0
    Trophy Points:
    1
    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.

    root@server [/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. :)
     
  3. SoftDux

    SoftDux Well-Known Member

    Joined:
    May 27, 2006
    Messages:
    983
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Johannesburg, South Africa
    cPanel Access Level:
    Root Administrator
    Does anyone know what causes this error, and how to fix it?

    Is it an actual problem with the DB?
     
  4. fijumen

    fijumen Member

    Joined:
    Jun 10, 2010
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    1
    Happened to me too, on a 2 new servers, must be a Munin bug, hope someone will update this thread after bug fix.
     
  5. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    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:

    Code:
    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:

    Code:
    vi /etc/munin/plugin-conf.d/mysql_innodb
    Place the following inside the file:

    Code:
    [mysql_innodb]
    env.warning 0
    env.critical 0
    At that point, run the following commands:

    Code:
    /etc/init.d/munin-node restart
    su munin -c /usr/bin/munin-cron
     
  6. alphawolf50

    alphawolf50 Well-Known Member

    Joined:
    Apr 28, 2011
    Messages:
    186
    Likes Received:
    2
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Also, if you use innodb_file_per_table, there is no point even running this plugin. It is safe to:

    Code:
    # 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
     
    #6 alphawolf50, Sep 10, 2011
    Last edited: Sep 10, 2011
  7. opentoe

    opentoe Active Member

    Joined:
    Feb 6, 2013
    Messages:
    40
    Likes Received:
    0
    Trophy Points:
    6
    cPanel Access Level:
    Website Owner
    This Munin "bug" is from 2011, and is still happening today in 2013?
     
  8. Astral God

    Astral God Well-Known Member

    Joined:
    Sep 27, 2010
    Messages:
    180
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    127.0.0.1
    cPanel Access Level:
    Root Administrator
    This is not a bug, but a "bad" default configuration of Munin; please read posts #6 and #7.
     
  9. kamm

    kamm Active Member

    Joined:
    Jan 17, 2004
    Messages:
    38
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Spain
    cPanel Access Level:
    Root Administrator
    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?
     
  10. Daky

    Daky Well-Known Member

    Joined:
    May 22, 2005
    Messages:
    56
    Likes Received:
    0
    Trophy Points:
    6
    I am getting the same message.

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

    Please advise
     
  11. musioc

    musioc Well-Known Member

    Joined:
    Aug 4, 2011
    Messages:
    105
    Likes Received:
    0
    Trophy Points:
    16
    Hello
    Same error :
    root@server [~]# su munin
    This account is currently not available.
     
  12. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    Hello :)

    You can run the following commands instead:

    Code:
    su - munin --shell=/bin/bash
    /usr/local/cpanel/3rdparty/perl/514/bin/munin-cron
    Thank you.
     
  13. mahesh123

    mahesh123 Well-Known Member

    Joined:
    Nov 2, 2013
    Messages:
    50
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    india
    cPanel Access Level:
    Root Administrator
    hello

    showing same warning ...


    Thank you ..
     
  14. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
  15. RobinF28

    RobinF28 Member

    Joined:
    Jun 27, 2015
    Messages:
    12
    Likes Received:
    2
    Trophy Points:
    3
    Location:
    Elgin, Scotland
    cPanel Access Level:
    Root Administrator
    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:

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

    root@srv [~]# vi /etc/munin/plugin-conf.d/mysql_innodb

    root@srv [~]# cat /etc/munin/plugin-conf.d/mysql_innodb
    [mysql_innodb]
    env.warning 0
    env.critical 0

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

    root@srv [~]# su munin -c /usr/bin/munin-cron
    This account is currently not available.

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

    munin@srv [~]# logout
    root@srv [~]#
     
    #15 RobinF28, Jan 21, 2016
    Last edited by a moderator: Aug 22, 2016
  16. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
  17. jmcguirl

    jmcguirl Registered

    Joined:
    Jul 29, 2007
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    1
    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.
     
Loading...

Share This Page