[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

logrotate problem, error renaming...File name too long



I've got a problem with my samba logs, which seems to be related to logrotate.  I'm hoping someone here can give me a clue on how to fix this problem.  The system this occurs on is running RH6.2, with all packages updated to current versions.


Here's the problem:


After several weeks of uptime, I get this message from logrotate:

errors occured while rotating /var/log/samba/log.*

error renaming /var/log/samba/log.localhost.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.7.gz to /var/log/samba/log.localhost.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.8.gz: File name too long
error renaming /var/log/samba/log.nmb.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.7.gz to /var/log/samba/log.nmb.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.8.gz: File name too long
error renaming /var/log/samba/log.pudge.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.7.gz to /var/log/samba/log.pudge.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.8.gz: File name too long
error renaming /var/log/samba/log.smb.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.7.gz to /var/log/samba/log.smb.1.gz.1.gz.1



A listing of /var/log/samba/ reveals:

log.localhost
log.localhost.1.gz
log.localhost.1.gz.1.gz
log.localhost.1.gz.1.gz.1.gz
log.localhost.1.gz.1.gz.1.gz.1.gz
log.localhost.1.gz.1.gz.1.gz.1.gz.1.gz
log.localhost.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
log.localhost.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
log.localhost.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
log.localhost.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
log.localhost.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
log.localhost.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
log.localhost.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz
log.localhost.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz

- big snip here -

log.smb.3.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz.1.gz

There are > 2500 files in /var/log/samba -- the vast majority of them with a size of 0 bytes, so it seems that these "log" files are not actually being used by Samba for any logging.

If I go into /var/log/samba/ and manually remove all of the "log" files, then things will appear to be OK for several more weeks (ie, no error messages from logrotate).  However, the problem will eventually resurface in exactly the same way, after several more weeks of uptime.



I'm guessing that logrotate is having problems properly closing, renaming, removing, etc the samba logs, but I'm not sure how to fix this problem.

Here's what's in /var/logrotate.d/samba:

/var/log/samba/log.* {
    notifempty
    missingok
    postrotate
	/usr/bin/killall -HUP nmbd
    endscript
}



And here's the contents of /etc/logrotate.conf:

#rotate log files daily
daily

# keep 7 days worth of backlogs
rotate 7

# send errors to
errors grover marshall edu

# create new (empty) log files after rotating old ones
create

# uncomment this if you want your log files compressed
compress

# RPM packages drop log rotation information into this directory
include /etc/logrotate.d

# no packages own lastlog or wtmp -- we'll rotate them here
/var/log/wtmp {
    monthly
    create 0664 root utmp
    rotate 1
}



Can I fix this problem by adding/changing a setting in one of the config files??

Any clues, hints, or solutions are greatly appreciated.

__
Larry Grover, PhD
Assoc Prof of Physiology
Marshall Univ Sch of Med






[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]