Logrotate error vsftpd.log

Hi People

Didn’t you just know I would be back with some troubles?

This is a clean install on CentOS 5.6

I am getting a cron error as follows :-

error: vsftpd.log:7 duplicate log entry for /var/log/xferlog
error: found error in /var/log/xferlog , skipping

Doing some digging around in /etc/logrotate.d I have vsftpd.log containing :

/var/log/vsftpd.log {
# ftpd doesn’t handle SIGHUP properly

/var/log/xferlog {
# ftpd doesn’t handle SIGHUP properly

Vsftp is installed but not running and I don’t intend to run it (or should I ?)

There is nothing like /var/log/xferlog

Proftp is running though I haven’t tested it.

Can I or should I uninstall vsftp and just use proftp ?
How can I stop the cron error ?

Or am I missing something?

Sorry to be a pain.

Thanks for reading

Operating system CentOS Linux 5.6
Webmin version 1.550
Virtualmin version 3.84 Pro
(the “Pro” is using the licence from another server pending migration from a compromised server)

It sounds like somehow, your system ended up with two logrotate entries for “/var/log/xferlog”.

I’d suggest just commenting one of them out, that should solve the error you’re getting.


Thanks Eric for your reply.

Where would I look for that?

I thought it would be in /etc/logrotate.d but there is only one vsftpd.logthere (content noted above).

Sorry to be so dim.


I would comment out the one you see in your vsftpd.log file, that would stop the problem you’re seeing.

The other entry may be in /etc/logrotate.conf, but that’s not the one I’d comment out, I’d comment out the first one you found in the vsftpd.log file.

Ah! Found the error and now it makes sense, almost.

Proftp is installed and running.
Vsftp is also installed but not running.

There is of course a cron job for Proftp but there is also another cron job for Vsftp. Both of these look at the same log file. Hence the error.

Strange though, The server that I am migrating from is the same spec and OS, that one has the same entries in logrotate.d but the lines in vsftpd.log are commented out. Both were installed on a fresh Centos using install.sh


Anyway, issue resolved even if the cause is not known.

Thanks Eric.