[mrtg] Large Master Config Vulnerability

Anson Rinesmith arinesmith at bigrivertelephone.com
Thu Apr 17 18:47:02 CEST 2008

You could always limit the number of retries.

A second option is to break up the master config file into other smaller
files, and therefore when something breaks only that smaller portion is
broken and the rest of your polls proceed without error.



From: mrtg-bounces at lists.oetiker.ch [mailto:mrtg-bounces at lists.oetiker.ch]
On Behalf Of Brad Lodgen
Sent: Thursday, April 17, 2008 11:39 AM
To: mrtg at lists.oetiker.ch
Subject: [mrtg] Large Master Config Vulnerability


Hi everyone,

I'm running a master config with hundreds of include lines and thousands of
targets. This type of setup is vulnerable to errors in config files and/or
changes made in the field not being immediately updated within the configs.
If there are a few errors or changes out in the field to ports causing them
to become 'unpollable', it causes the MRTG polling interval to go over five
minutes because it's retrying those interfaces. At the moment, with only
about 30 error lines in my log(equating to about 15 interfaces/targets),
it's causing MRTG to take 7-9 minutes to complete polling. As this is a very
small percentage compared to the total amount of targets being polled, I'm
trying to figure out a way to get around this, if possible, or at least to
minimize the effects.

Is anyone else running a system like this or does anyone have suggestions to

Thanks in advance for any help!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.oetiker.ch/pipermail/mrtg/attachments/20080417/ce0e314e/attachment.html 

More information about the mrtg mailing list