Page 1 of 1

mrtg error

Posted: Mon Jul 15, 2013 3:19 am
by zaji_nms
Dear Support,

we are running nagiosxi 2012R1.7 on following platform we are getting error in mrtg file . at present file size is 3.2Mb and we will be adding up to 30Mb . we need immediate solution or fix for it.

Linux c1nms.zajil.com 2.6.32-358.2.1.el6.x86_64 #1 SMP Wed Mar 13 00:26:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[root@c1nms mrtg]# ll
total 16100
-rw-r--r-- 1 root root 3210270 Jul 15 09:47 mrtg.cfg


2013-07-15 09:50:01 -- 2013-07-15 09:50:01: ERROR: I guess another mrtg is running. A lockfile (/var/lock/mrtg/mrtg_l) aged
300 seconds is hanging around. If you are sure that no other mrtg
is running you can remove the lockfile
2013-07-15 09:55:01 -- Started mrtg with config '/etc/mrtg/mrtg.cfg'
2013-07-15 10:55:01 -- Started mrtg with config '/etc/mrtg/mrtg.cfg'
2013-07-15 11:00:01 -- Started mrtg with config '/etc/mrtg/mrtg.cfg'
2013-07-15 11:00:01 -- 2013-07-15 11:00:01: ERROR: I guess another mrtg is running. A lockfile (/var/lock/mrtg/mrtg_l) aged
300 seconds is hanging around. If you are sure that no other mrtg
is running you can remove the lockfile

Re: mrtg error

Posted: Mon Jul 15, 2013 9:09 am
by slansing
Do you have multiple MRTG.cfg files split apart? Do you have a extended timeout on any of the objects within this config, or these configs?

Please share the output of the following:

Code: Select all

cat /etc/cron.d/mrtg

Re: mrtg error

Posted: Tue Jul 16, 2013 1:12 am
by zaji_nms
no we dont have multiple mrtg.cfg nor its splited. all hosts avg response time is between 1-10ms.
--------------------------------------------------------------------------------------------------------------------
*/5 * * * * root LANG=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg --lock-file /var/lock/mrtg/mrtg_l --confcache-file /var/lib/mrtg/mrtg.ok --logging /var/log/mrtg.log

Re: mrtg error

Posted: Tue Jul 16, 2013 10:06 am
by lmiltchev
Is you system under heavy load during certain periods? It's possible that your polling is taking longer than the 5 min interval you've set in the crontab. Try changing the interval to 10 min (for testing purposes), and see if this is going to eliminate the issue.