<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3268" name=GENERATOR><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=375220917-17042008>I have all my configs in one directory and run mrtg as
a cron job with the following script.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=375220917-17042008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=375220917-17042008>#! /bin/bash</SPAN></FONT></DIV>
<DIV> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=375220917-17042008>for fn in /etc/mrtg/*.cfg;
do<BR> env LANG=C /usr/bin/mrtg "$fn"
&<BR>done</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=375220917-17042008></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=375220917-17042008>Maybe this will would for you. I have been down
the include route and I agree it does cause problems.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=375220917-17042008></SPAN></FONT> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mrtg-bounces@lists.oetiker.ch
[mailto:mrtg-bounces@lists.oetiker.ch] <B>On Behalf Of </B>Anson
Rinesmith<BR><B>Sent:</B> Thursday, April 17, 2008 11:47 AM<BR><B>To:</B> 'Brad
Lodgen'; mrtg@lists.oetiker.ch<BR><B>Subject:</B> Re: [mrtg] Large Master Config
Vulnerability<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">You could always limit
the number of retries.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT
face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT
face=Tahoma size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">
mrtg-bounces@lists.oetiker.ch [mailto:mrtg-bounces@lists.oetiker.ch] <B><SPAN
style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>Brad Lodgen<BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> Thursday, April 17, 2008 11:39
AM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B>
mrtg@lists.oetiker.ch<BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B>
[mrtg] Large Master Config Vulnerability</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt">Hi everyone,<BR><BR>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.<BR><BR>Is anyone else running a system like this
or does anyone have suggestions to try?<BR><BR>Thanks in advance for any
help!<BR>Brad<o:p></o:p></SPAN></FONT></P></DIV><p></p><p>Please consider the environment before printing this e-mail. <br><br> CONFIDENTIAL NOTICE:<br>This e-mail message and any attachment(s) (collectively, this 'Email') are intended <br>only for the confidential use of the recipient(s) named above. If the reader of this <br>message is not the intended recipient named above or an agent responsible for <br>delivering it to the intended recipient named above, you have received this Email in error. <br>Please notify the sender immediately and permanently delete this Email and any copies thereof.</BODY></HTML>