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, suddenly has a high "update" time

Discussion in 'General Discussion' started by GoWilkes, Aug 27, 2012.

  1. GoWilkes

    GoWilkes Well-Known Member

    Joined:
    Sep 26, 2006
    Messages:
    367
    Likes Received:
    1
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    I uploaded a new httpd.conf file last night, changing one medium-traffic parked domain to point to a new account. Since then, everything looks normal under Munin, except for one stat: Munin Processing Time.

    Before uploading the new httpd.conf, the "munin update" field stayed at around 6.5 seconds. Now, it's staying steady at around 19.5 seconds. It's not fluctuating with server load or anything, so I'm not sure why it's lagging, or if it's pulling resources from something else.

    I had another issue where two different site users were using a script that writes to MySQL, and they said that it just kept processing and never wrote. All of the MySQL and Apache stats look normal, though (in fact, most seem a little lower than before the change, which is good), so I suspect that the "munin update" field is an indicator of another issue that I'm not seeing.

    Any suggestions?
     
  2. GoWilkes

    GoWilkes Well-Known Member

    Joined:
    Sep 26, 2006
    Messages:
    367
    Likes Received:
    1
    Trophy Points:
    18
    cPanel Access Level:
    Root Administrator
    Update:

    I found the file "munin-update.log" at /var/log/munin, and it shows this just before I changed httpd.conf:

    Code:
    2012/08/27 04:20:36 Opened log file
    2012/08/27 04:20:36 [INFO]: Starting munin-update
    2012/08/27 04:20:36 [ERROR] In RRD: Error updating /var/lib/munin/example.com/servername.com-bonding_err_bond0-if_eth0-d.rrd: /var/lib/munin/example.com/servername.com-bonding_err_bond0-if_eth0-d.rrd: not a simple signed integer: 'if_eth2.value'
    2012/08/27 04:20:36 [WARNING] Service bonding_err_bond0 on servername.com/127.0.0.1:4949 returned no data for label if_eth2
    2012/08/27 04:20:36 [ERROR] In RRD: Error updating /var/lib/munin/example.com/servername.com-bonding_err_bond1-if_eth1-d.rrd: /var/lib/munin/example.com/servername.com-bonding_err_bond1-if_eth1-d.rrd: not a simple signed integer: 'if_eth3.value'
    2012/08/27 04:20:36 [WARNING] Service bonding_err_bond1 on servername.com/127.0.0.1:4949 returned no data for label if_eth3
    2012/08/27 04:20:42 [WARNING] Service yum on servername.com/127.0.0.1:4949 returned no data for label pending
    2012/08/27 04:20:42 [INFO] Reaping Munin::Master::UpdateWorker<example.com;servername.com>.  Exit value/signal: 0/0
    2012/08/27 04:20:42 [INFO]: Munin-update finished (6.36 sec)
    
    Note the last line, where it took 6.36 seconds to finish. Then immediately after changing the httpd.conf file:

    Code:
    2012/08/27 04:25:36 Opened log file
    2012/08/27 04:25:36 [INFO]: Starting munin-update
    2012/08/27 04:25:36 [ERROR] In RRD: Error updating /var/lib/munin/example.com/servername.com-bonding_err_bond0-if_eth0-d.rrd: /var/lib/munin/example.com/servername.com-bonding_err_bond0-if_eth0-d.rrd: not a simple signed integer: 'if_eth2.value'
    2012/08/27 04:25:36 [WARNING] Service bonding_err_bond0 on servername.com/127.0.0.1:4949 returned no data for label if_eth2
    2012/08/27 04:25:37 [ERROR] In RRD: Error updating /var/lib/munin/example.com/servername.com-bonding_err_bond1-if_eth1-d.rrd: /var/lib/munin/example.com/servername.com-bonding_err_bond1-if_eth1-d.rrd: not a simple signed integer: 'if_eth3.value'
    2012/08/27 04:25:37 [WARNING] Service bonding_err_bond1 on servername.com/127.0.0.1:4949 returned no data for label if_eth3
    
    ***
    2012/08/27 04:25:46 [INFO] Remaining workers: example.com;servername.com
    2012/08/27 04:25:50 [WARNING] Service http_loadtime on servername.com/127.0.0.1:4949 returned no data for label loadtime
    ***
    
    2012/08/27 04:25:55 [WARNING] Service yum on servername.com/127.0.0.1:4949 returned no data for label pending
    2012/08/27 04:25:55 [INFO] Reaping Munin::Master::UpdateWorker<example.com;servername.com>.  Exit value/signal: 0/0
    2012/08/27 04:25:55 [INFO]: Munin-update finished (19.17 sec)
    
    This time, it took 19.17 seconds to finish! So, I must have changed something in httpd.conf.

    I added the *** in the second list to denote the new errors. They are:

    Code:
    2012/08/27 04:25:46 [INFO] Remaining workers: example.com;servername.com
    2012/08/27 04:25:50 [WARNING] Service http_loadtime on servername.com/127.0.0.1:4949 returned no data for label loadtime
    
    I have no idea what "remaining workers" means, but I do know that "HTTP Loadtime" is now giving a NAN error. So this seems to be the source of the increased run time, but... now what?
     
Loading...

Share This Page