I break my master config into smaller configs. I then go one step further and 
run six instances of MRTG, one for each config. I'm polling at one minute 
intervals, so this is a necessity for me.

How do you limit the number of retries?

Thanks,
Garry

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anson Rinesmith
Sent: Thursday, April 17, 2008 10:47 AM
To: 'Brad Lodgen'; [email protected]
Subject: Re: [mrtg] Large Master Config Vulnerability

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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brad Lodgen
Sent: Thursday, April 17, 2008 11:39 AM
To: [email protected]
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 
try?

Thanks in advance for any help!
Brad

________________________________
NOTICE: This e-mail and any files transmitted with it are the property of 
ARCADIS U.S., Inc. and its affiliates. All rights, including without limitation 
copyright, are reserved. The proprietary information contained in this e-mail 
message, and any files transmitted with it, is intended for the use of the 
recipient(s) named above. If the reader of this e-mail is not the intended 
recipient, you are hereby notified that you have received this e-mail in error 
and that any review, distribution or copying of this e-mail or any files 
transmitted with it is strictly prohibited. If you have received this e-mail in 
error, please notify the sender immediately and delete the original message and 
any files transmitted. The unauthorized use of this e-mail or any files 
transmitted with it is prohibited and disclaimed by ARCADIS U.S., Inc. and its 
affiliates.
_______________________________________________
mrtg mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg

Reply via email to