[mrtg] Unknown data issues

robert.harrowfield at axon.co.nz robert.harrowfield at axon.co.nz
Mon Mar 25 01:47:24 MET 2002


Hi all,

Thanks for the couple of responses I had when I initially posted this query,
its appreciated. Im not sure wether I should be posting this to the general
mrtg list, or to the dev list??

Im having a bit of an issue with MRTG acting like its defaulting to
UNKASZERO when an SNMP query fails to retrieve data from a remote source.
Ive pasted a couple of sections of logs below that demonstrate what is
happening. 

Up until recently, I was running MRTG 2.8.something and this worked fine, if
the snmp source was unavailable, it just kept repeating its last known good
value, keeping a nice flat graph, rather than dropping to zero. I had to
update to a newer version to get the forking and daemon functionality that
is now in MRTG (thanks Tobi!!) and so got v2.9.18pre1. This started giving
me the problem with unknown data (when a server isnt available) causing
large troughs in my graphs and dropping down to zero it the host is
unavailable for enough 5 min periods.

I then tried v2.9.18pre2 (and also pre3 this morning) with no better
success. Normally I wouldnt deem this to be a real issue, but we also use
MRTG for polling the available HDD space on NT servers for customers. We use
minimum threshold alerts for diskspace available, which final destination is
an on-call engineer's pager. Understandably, the engineers get more than a
little grumpy when the pager wakes them at 2am, just because a few snmp
packets have gone AWOL. 



mrtglog
usr/local/mrtg-2/bin/mrtg line 1521
2002-03-21 17:22:50 -- WARNING: Expected a number but got ''
2002-03-21 17:22:50 -- WARNING: Expected a number but got ''
2002-03-21 17:23:01 -- SNMP Error:
no response received

logfile for disk during dip period
1016688160 -1 -1
1016688160 1 1 1 1
1016687843 8443 8443 8443 8443
1016687700 8698 8698 8986 8986
1016687400 9307 9307 9675 9675
1016687100 9737 9737 9807 9807
1016686800 9810 9810 9815 9815
1016686500 9816 9816 9819 9819

logfile about 5 mins after dip period
1016688443 7545 7545
1016688443 7545 7545 7545 7545
1016688160 1 1 1 1
1016688000 4025 4025 8443 8443
1016687700 8698 8698 8986 8986
1016687400 9307 9307 9675 9675

logfile 10 mins after dip period
1016688741 7351 7351
1016688741 7351 7351 7351 7351
1016688443 7545 7545 7545 7545
1016688300 3521 3521 7545 7545
1016688000 4025 4025 8443 8443
1016687700 8698 8698 8986 8986
1016687400 9307 9307 9675 9675
1016687100 9737 9737 9807 9807

section of config file (all other entries similar)
Target[server1.memory]:
.1.3.6.1.4.1.311.1.1.3.1.1.1.1.0&.1.3.6.1.4.1.311.1.1.3.1.1.1.2.0:community@
server
Options[server.memory]: gauge, nopercent
AbsMax[server.memory]: 529088512
MaxBytes1[server.memory]: 267837440
MaxBytes2[server.memory]: 529088512
Unscaled[server.memory]: dwmy
YLegend[server.memory]: Bytes
ShortLegend[server.memory]: Bytes
Legend1[server.memory]: Availble Memory
Legend2[server.memory]: Committed Memory
LegendI[server.memory]:  Available:
LegendO[server.memory]:  Committed:
ThreshMaxO[server.memory]: 396816384
ThreshProgO[server.memory]: /usr/local/bin/tecalert.customer.pl
Title[server.memory]: SERVER: Available Real / Committed Virtual Memory
PageTop[server.memory]: <h1>GPNTS01: Available Real / Committed Virtual
Memory</h1>
  Total Physical Memory: 256 MB
  <div align="center"><center>


Any help that anyone can provide will be greatly appreciated.
Rob.


-- 
The information contained in this e-mail message is intended only for the use of the person or entity to whom it is addressed and may contain information that is CONFIDENTIAL and may be exempt from disclosure under applicable laws. 

If you read this message and are not the addressee you are notified that use, dissemination, distribution, or reproduction of this message is prohibited. If you have received this message in error, please notify us immediately and delete the original message. You should scan this message and any attached files for viruses. 

Axon Computertime accepts no liability for any loss caused either directly or indirectly by a virus arising from the use of this message or any attached file.

--
Unsubscribe mailto:mrtg-request at list.ee.ethz.ch?subject=unsubscribe
Archive     http://www.ee.ethz.ch/~slist/mrtg
FAQ         http://faq.mrtg.org    Homepage     http://www.mrtg.org
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi



More information about the mrtg mailing list