[mrtg] RateUP WARNING : Can`t rename error

[Chris Blake]

On Thu, 2011-02-17 at 21:23 +0000, Steve Shipway wrote:
> If you are getting these messages often - and for the same file! - then there is a real problem on your system that needs to be addressed.
> * If you have a successful run (no error) and then later an unsuccessful one, something is breaking.
> 
> * One possibility is that you have some periodic 'clean-up; job running on your system that is deleting .log files.  
> In this case, stop it!  You can tell if this is the case because you will lose your history from the file each time it is deleted 
> -- do your weekly graphs never seem to grow longer?

Hi Steve,

The graphs are showing correctly, since June last year, without any
noticeable deviations from the norm. 

> * Maybe your filesystem is getting very full, and occasionally fills up, so you are unable to make these changes.  
> This would not be so likely to prevent a rename, though it might cause the log file to fail to be recreated which 
> would give the error on the next pass.  Check you have sufficient free space!

"df -hl" reports all good there.

> * Check filesystem, directory and file ownerships and permissions.  
> This shouldn’t be a problem, but if you are running multiple daemons or jobs you may have something confused.

crontab does not show any jobs doing this, what I did see was these
entries in the 127.0.0.1_2.log

<snipped logs>
1277078400 677 2149 33345 30255
1276992000 799 2666 34146 40597
1276905600 2000 4900 40239 31721
1276819200 1519 5086 34751 40399
1276732800 895 3400 46505 39118
1276646400 652 1976 97123 291571
1276560000 0 0 0 0
1276473600 0 0 0 0
1276387200 0 0 0 0
1276300800 0 0 0 0
1276214400 0 0 0 0
1276128000 0 0 0 0
1276041600 0 0 0 0
</snipped logs>

A few moments later, as per the directory ls below, I noticed that the
127.0.0.1_2.log file vanished for about 2 minutes, and then mysteriously
re-appeared, filled with entries ?
 
> Lack of write permission to the directory will give a rename error.

I have the following permissions on the mrtg web files :

-rw-rw-rw- 1 root root  9189 Feb 18 15:48 127.0.0.1_2-day.png
-rw-rw-rw- 1 root root  6120 Feb 18 15:48 127.0.0.1_2.html
-rw-r--r-- 1 root root 73703 Feb 18 15:48 127.0.0.1_2.log
-rw-rw-rw- 1 root root  8228 Feb 18 15:00 127.0.0.1_2-month.png
-rw-r--r-- 1 root root 73703 Feb 18 15:46 127.0.0.1_2.old
-rw-rw-rw- 1 root root  8152 Feb 18 15:24 127.0.0.1_2-week.png
-rw-rw-rw- 1 root root  6067 Feb 17 17:15 127.0.0.1_2-year.png
lrwxrwxrwx 1 root root    45 Jun 15  2010 index.html -> /<web server
path>/mrtg/127.0.0.1_2.html
-rw-rw-rw- 1 root root   538 Jun 15  2010 mrtg-l.png
-rw-rw-rw- 1 root root   414 Jun 15  2010 mrtg-m.png
-rw-rw-rw- 1 root root  1759 Jun 15  2010 mrtg-r.png

This is right, I think. Should these be owned by anyone else,
apache:apache ?

I have cross checked these permissions against another server we have
and that one is also listing root:root, and works fine.

I do appreciate your reply and willingness to assist, thank you very
much.

Regards

-- 
Chris Blake
chris at igroup.co.za

Tel: 0861 IGROUP (447 687) Ext: 2280   |    Int: +27 11 712-3900    |
Fax: 011 507-5749    |   www.igroup.co.za

iGroup Call Centre Outsourcing – email sales at igroup.co.za

Delays in responding to emails will result in delays in project
completion dates and may incur additional charges. Use of this e-mail
and any attachments to it is subject to our e-mail Terms and Conditions
located at http://www.igroup.co.za/legal/email-disclaimer.htm - please
review these now. If you cannot access them, please call 0861 447 687 or
INT +27 11 712-3900 or email info at igroup.co.za