Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: Tim Gibson on September 11, 1999, 03:42:34 AM

Title: Error rotating logs
Post by: Tim Gibson on September 11, 1999, 03:42:34 AM
I get this e-mail from my e-smith 3.0 server:

errors occured while rotating /var/log/xferlog

stat of /var/log/xferlog failed: No such file or directory

I tried creating an empty file in the specified location but it cropped up again.
Title: RE: Error rotating logs
Post by: Kim Morrison on September 14, 1999, 09:25:06 PM
Hi Tim!

A few of our test systems also generate this error message.  We believe this to be harmless and we'll fix this error generation in the next release.

Thanks for the post!

Kim
Title: RE: Error rotating logs
Post by: arthur on September 17, 1999, 02:27:08 AM
Hi Tim,

There is a way to get around of this so you won't get this nasty error. However, it's not the best idea to do, but if you're not using ftp at all, it might be worth it.

The logrotation process is done by a cron job in /etc/cron/cron.daily From there it starts the program "logrotate" which has it's config file in /etc/logrotate.conf. In there you'll find that more config options are comming from /etc/logrotate.d Now, to make sure you don't get these errors anymore, just open up ftpd in an editor and comment everything out and you're done!

Please note that when you'll start using the ftp-service, eventually your logs may start growing. In a worst case scenario, this could fill your disk, preventing your system from working! So, the choice is yours: getting the e-mail or live on the risky side!

bibi,
arthur
Title: RE: Error rotating logs
Post by: Charlie Brady on September 17, 1999, 08:10:18 AM
>A few of our test systems also generate this >error message.  We believe this to be >harmless and we'll fix this error generation >in the next release.

I think that adding "missingok" to /etc/logrotate.d/ftpd should fix this.
Title: RE: Error rotating logs
Post by: Kim Morrison on September 17, 1999, 06:57:48 PM
Thanks, Charlie!

K.