[mrtg] MRTG resets all graphs daily, why?

[Mick]

On Friday 05 June 2009, Alex van den Bogaerdt wrote:
> ----- Original Message -----
> From: "Adam Williams" <awilliam at mdah.state.ms.us>
> To: "Alex van den Bogaerdt" <alex at vandenbogaerdt.nl>
> Cc: <mrtg at lists.oetiker.ch>
> Sent: Friday, June 05, 2009 3:42 PM
> Subject: Re: [mrtg] MRTG resets all graphs daily, why?
>
> > This is what I'm getting in emails from cron about mrtg.  It says rateup
> > can't rename log files.  Which is strange, mrtg is being ran as root in
> > cron, so there should be no problems with file permissions, and there's
> > plenty of free disk space from my last email (18% free).  Any ideas?
> >
> > Date: Fri,  5 Jun 2009 08:40:07 -0500 (CDT)
> > From: Cron Daemon <root at missioncontrol.squeezer.net>
> > To: root at missioncontrol.squeezer.net
> > Subject: Cron <root at missioncontrol> env LANG=C /usr/bin/mrtg
> >    /etc/mrtg/mrtg.cfg --logging /var/log/mrtg.log
> >
> > 2009-06-05 08:40:07, Rateup WARNING: /usr/bin/rateup could not read the
> > primary log file for localhost_68.209.223.242
> > 2009-06-05 08:40:07, Rateup WARNING: /usr/bin/rateup Can't remove
> > localhost_68.209.223.242.old updating log file
> > 2009-06-05 08:40:07, Rateup WARNING: /usr/bin/rateup Can't rename
> > localhost_68.209.223.242.tmp to localhost_68.209.223.242.log updating log
> > file
>
> Looks like there is no result when mrtg runs, thus there is no new log
> file, thus it cannot be renamed next time, and so on.
>
> You will need to find out why mrtg fails to do its stuff. Sorry, can't help
> here, someone else has to.

As Alex says, when mrtg runs for the first few times it will generate such 
messages.  Is it OK after say half hour of running?

If you still have problems, then check anything else that affects ownership 
and access rights - e.g. do you run SELinux on this box?

Running mrtg as root is not a good idea, I suggest that you run it as a plain 
user after you change ownership of e.g. the group of the directory within 
which the files are saved as appropriate, so that mrtg can save it's logs in 
there.
-- 
Regards,
Mick
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://lists.oetiker.ch/pipermail/mrtg/attachments/20090606/8cc423ab/attachment.bin