Critical Warning from Munin

hrace009

• September 02, 2016 11:30

Hello, I just re-installed my cpanel win centos 7 Currently i installed Munin Service Monitor from WHM. I got CRITICAL warning like this: 40551 I don't understand why it Critical. since it still only 1 domain. should i ignore this critical warning?

• 

  Infopro

  • September 02, 2016 17:27

  Currently i installed Munin Service Monitor from WHM

  
  How long ago? Could it be that it's just not generated any stats yet (I'm guessing)? Lots of posts via google about this: Here's one with the exact same message as yours from 2013: MySQL Lists: mysql: munin MyISAM & InnoDB issues Here's the Munin docs: fieldname.critical " Munin

  0
• 

  hrace009

  • September 02, 2016 17:33

  How long ago?

  
  around 1 hour after i install munin from WHM.

  Could it be that it's just not generated any stats yet (I'm guessing)?

  
  i am not sure, but i will keep monitoring it. who knows it will change by it self. but at this moment, everything running fine on my web server.

  Here's one with the exact same message as yours from 2013: MySQL Lists: mysql: munin MyISAM & InnoDB issues Here's the Munin docs: fieldname.critical " Munin

  
  Thanks, i will try to find it out EDIT--------- I am using MariaDB

  0
• 

  cPanelMichael

  • September 02, 2016 20:25

  Hello, You can manually initiate the munin update process via the following commands while logged in as "root" via SSH:
  su - munin --shell=/bin/bash /usr/local/cpanel/3rdparty/perl/522/bin/munin-cron exit
  Let us know if this helps. Thank you.

  0
• 

  hrace009

  • September 02, 2016 20:31

  Hello, You can manually initiate the munin update process via the following commands while logged in as "root" via SSH:
  su - munin --shell=/bin/bash /usr/local/cpanel/3rdparty/perl/522/bin/munin-cron exit
  Let us know if this helps. Thank you.

  
  hi, i create this
  /etc/munin/plugin-conf.d/mysql_innodb.conf
  and add
  [mysql_innodb] env.warning 0 env.critical 0
  then restart munin service and run
  su - munin --shell=/bin/bash /usr/local/cpanel/3rdparty/perl/522/bin/munin-cron exit
  now the notification gone.

  0
• 

  cPanelMichael

  • September 02, 2016 20:36

  Hello, I'm happy to see you were able to address the issue. Could you verify if you checked to see if the issue occurred after running the munin-cron command referenced in my last response? Or, did the issue persist until you added those entries to the /etc/munin/plugin-conf.d/mysql_innodb.conf file? Thank you.

  0
• 

  hrace009

  • September 02, 2016 20:55

  Hello, I'm happy to see you were able to address the issue. Could you verify if you checked to see if the issue occurred after running the munin-cron command referenced in my last response? Or, did the issue persist until you added those entries to the /etc/munin/plugin-conf.d/mysql_innodb.conf file? Thank you.

  
  I have try to remove /etc/munin/plugin-conf.d/mysql_innodb.conf and restart the service, then re running
  su - munin --shell=/bin/bash /usr/local/cpanel/3rdparty/perl/522/bin/munin-cron exit
  The problem still persist. But if i create
  /etc/munin/plugin-conf.d/mysql_innodb.conf
  CRITICAL warning gone. i think that config only make it ignore about mysql_innodb

  0
• 

  cPanelMichael

  • September 06, 2016 21:04

  For anyone that wants more information on that InnoDB warning, the following thread should help to explain why that happens: MUNIN Plugin WARN: MySQL InnoDB free tablespace Thank you.

  0

Please sign in to leave a comment.