[mrtg] Re: 2 hourly collections not collecting

Bryan Socha byans at ugo.com
Thu Feb 24 11:11:43 MET 2000


The poll for memory is quick and barely any net traffic, is it really a
problem if you don't poll every 5 minutes?


Bryan Socha
Network Engineer
UGO Networks, Inc.

Phone: 212-624-3362
Cell: 917-439-5503

-----Original Message-----
From: Matthew Moore (DSL AK) [mailto:MattM at datacom.co.nz]
Sent: Tuesday, February 22, 2000 3:10 PM
To: 'mrtg at list.ee.ethz.ch'
Subject: [mrtg] Re: 2 hourly collections not collecting


I have changed the target name, but the cfg file is fine, because if I just
change the Interval to 5 minutes (in the original cfg), then the logs and
graphs are generated fine (I just don't want to poll this often).

Regards,
 Matt Moore


-----Original Message-----
From: Leif Neland [mailto:leifn at neland.dk]
Sent: Tuesday, 22 February 2000 18:45
To: Matthew Moore (DSL AK)
Cc: 'mrtg at list.ee.ethz.ch'
Subject: [mrtg] Re: 2 hourly collections not collecting




On Tue, 22 Feb 2000, Matthew Moore (DSL AK) wrote:

> Hi,
> 
> I am trying to graph cisco freeMem (.1.3.6.1.4.1.9.2.1.8) data on a 2
hourly
> interval (and only displaying monthly and yearly graphs), as I feel a
> shorter polling interval is not necessary. My problem is that the log file
> is not being updated. It always just has the last poll, with no historical
> data (Yes, mrtg is definitely running every 2 hours). Eg:
> 
> 951176704 2548484 2548344
> 951176704 0 0 0 0
> 951176400 0 0 0 0
> 951176100 0 0 0 0
> <snip>....
> 
> An snmpwalk does return the correct value. Also if I set the Interval to
> less than 1 hour, the log files and graphs are correct. I've tried using
> both RunAsDaemon, and the Windows scheduler to run the cfg file, but the
> result is the same. There are also no output errors after running. I also
> have several other 5 minute interval cfg files running without problems.
> 
> The important lines in the cfg file are as follows:
> 
> WorkDir: c:\InetPub\wwwroot\mrtg
> Interval: 120
> #====================================================================
> Target[abc.freeMem]:
1.3.6.1.4.1.9.2.1.8.0&1.3.6.1.4.1.9.2.1.8.0:public at abc
> MaxBytes[abc.freeMem]: 20000000
> Options[abc.freeMem]: gauge

It appears "gauge" is not working. Is this the real cfg, or has you
changed the name of the router for security reasons?
If so, are you sure you haven't missspelled the target name?

Leif


--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:mrtg-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/mrtg

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:mrtg-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/mrtg

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:mrtg-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/mrtg



More information about the mrtg mailing list