2011-09-12 05:50:25 -- 2011-09-12 05:50:20: WARNING: rateup died from Signal 0 with Exit Value 1 when doing router 'rejectscnt' Signal was 0, Returncode was 1
So, rateup is exiting with an error status, which causes MRTG to stop processing the target. The problem lies in rateup (so you're using native mode MRTG, of course). A signal=0 means a normal exit, but returncode=1 means a fail status, so not a crash. There are a huge number of possible things that can give this exit code - out of memory, unable to open file, date string too long, filename too long, unable to write to file, corrupted backup log file. Although rateup produces an output indicating the error it is not preserved by MRTG, I think. If you catch the stdout/stderr output of the MRTG run then it may be in there rather than the logfile. I would check ownerships and permissions on the files and filesystem (is it read-only?) and check for log file corruption. Steve _____ Steve Shipway ITS Unix Services Design Lead University of Auckland, New Zealand Floor 1, 58 Symonds Street, Auckland Phone: +64 (0)9 3737599 ext 86487 DDI: +64 (0)9 924 6487 Mobile: +64 (0)21 753 189 Email: <mailto:[email protected]> [email protected] P Please consider the environment before printing this e-mail
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
