We can see that rateup is exiting with an error but not see the error message being produced by rateup (only the error being produced by mrtg, which calls it)
You need to test rateup somehow. Try running rateup from the command line to directly update one of your log files (I forget the exact syntax required as I haven't touched rateup in over 10 years); you might get some infor this way. Possibly your .log files are corrupted, or have incorrect permissions or ownerships? 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 From: Matt Baer [mailto:[email protected]] Sent: Thursday, 6 October 2011 2:13 a.m. To: Steve Shipway Cc: mrtg Subject: Re: [mrtg] Graphs Resetting & Freezing The stderr/stdout shows the same thing that appears in the logs. On Thu, Sep 15, 2011 at 3:22 PM, Steve Shipway <[email protected]> wrote: mrtg is not a shell script, its a perl script. So, you dont call it with 'sh -x', you call it with 'perl'. Otherwise you get error messages as the shell interpreter gets confused by the perl code. You can increase the logging in MRTG, but the error appears to be in the rateup call rather than in MRTG. You need to capture the stdout/stderr from the mrtg call so that you see any error messages produced by rateup calls, this might give more light on the reason for the rateup error exit. Steve Steve Shipway University of Auckland ITS UNIX Systems Design Lead [email protected] Ph: +64 9 373 7599 ext 86487 <tel:%2B64%209%20373%207599%20ext%2086487>
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ mrtg mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/mrtg
