nixCraft

Hi

I've got MRTG running for a while now but after 4 ÃÂ* 5 days it stops logging to the graph.
We used to run MRTG on a NT4 workstation but after a network migration to windows server 2003 we transfered MRTG to a windows XP workstation.
Since then MRTG stops logging after several days
We've been spending much time trying to solve this problem
any Idea's what the cause of this problem could be????

I'd appreciate it

1) Make sure it is running in background. What software you use to run mrtg in background or else add following line to your mrtg.cfg file
And start service as follows:
2) Assuming that you have atleast following installed correctly
mrtg
Perl (ActivePerl)

3) In order to debug it following options you need to pass to mrtg
Option to pass mrtg:
--logging=c:\mrtg.log

c:\mrtg.log will log all messages.

--debug="snpo,cfg"
Where,
snpo – will display you snmp polling
cfg – will log the config file reading

For example here is full command to mrtg debug at C:\ dos prompt (cmd.exe)
Make sure you point correct cfg file (yourmrtg.cfg)

This will trace your snmp polling and log them to file c:\mrtg.log

This is the only way to find out what's goint wron with it. Once you got it paste back here your file so that can we can find out more. Also note other debug options

cfg - watch the config file reading
dir - directory mangeling
base - basic program flow
tarp - target parser
snpo - snmp polling
fork - forking view
time - some timing info
log - logging of data via rateup or rrdtool


I have not used mrtg much on windows but used a lot on UNIX like os. Hope this helps.

I used the runAsDaemon: yes option
And the following commandline to start the service

start /Dc:\mrtg-2.0.13\bin wperl mrtg --logging=eventlog cpu.cfg
Or for my test enviroment i first got to the bin dir and then typed
start wperl mrtg --logging=eventlog cpu.cfg

It logs fine for a couple of days but then it stops

I checked out my OID's and they where al correct
My graphs didn't seem to show strange values or something
except for the CPU load in %
It gives a pink line in the weekly monthly an yearly graph
but that just has to do with the "withpeak" command

Okay try one command and open NT/XP logviewer tool and see what it logs:

It didn't log anything wrong

But...

I got this error in eventview after 2 days of logging it said.

Warning: rateup died from signal 0
with exit value 1 when doing router xxxxx_xxxxxx
Signal was 0, Returncode was 1.

And this:

SNMP Error:
no response received
SNMPV1_Session (remote host: "IP.xxx.xx.xx. [xxx.xxx.xxx.xxx].161)
Community: "xxxxxxx"
request ID: 994981897
PDU bufsize: 8000 bytes
Timeout: 2s
retries 5
backoff : 1

And this:

SNMPGET Problem for ifInOctets.65539 ifOutOctets.65539 sysuptime
Sysname on community@IPadress::::::::::V4only

And another thing

When I trie to get value's from a HDD that's in the fileserver
with GetIf it gives only 2 values and it should give 4 values
it has 3 partitions so it should display C: D: E: and total
But I only get 2 values.

I'm now trying it with the debug option given to me in the last reply

In about 2 days i'll know what it has to say about mrtg when it stops logging then i'll post a copy of the errors on this forum

thanks for ur hellp

I tried it with the debug options

No errors appeared in the log files

Everything seemed fine but on the saturday it was interupted

No errors
Log file just stopped
At the time MRTG stopped logging
It kept daemonizing but doesn't log anything to the graphs or the log file

It stopped logging again saturday night
with the following error message in eventlog

Windows cannot acces file gpt.ini
for GPO CN={31b2f340-016d-11d2-945f-00c04fb984f9}
CN=Policies,CN=System,DC=Domain, DC=Local
<\\domain.local\sysvol\domail.local\Policies\{31b2 f340-016d-11d2-945f-00c04fb984f9}\gpt.ini>
(Configuration information could not be read from the domain controller, either because the machine in unavailable, or acces has been denied.).
Group policy processing aborted

I don't know what i can do about this problem or if it is causing the problems with mrtg but maybe someone knows the problem

Or can help me with it.

Looks like it is NT/2000/XP policy problem

Yes I got it solved