Hi Team. I've been looking at the proftpd problems that have been recently reported, and I have some good news. I've tested, and I believe I have a fix. This is actually I think a bug that has been around for a very long time back to the BlueQuartz days. The weird thing is that this problem was not happening uniformly on all servers.... and it used to "come and go" after different updates.
Here's what I found in the log files.... Jun 5 10:00:01 node1 xinetd[24021]: START: ftp pid=3620 from=127.0.0.1 Jun 5 10:00:01 node1 proftpd[3620]: warning: "ProFTPD" address/port (203.26.211.121:21) already in use by "ProFTPD server" Jun 5 10:00:01 node1 xinetd[24021]: EXIT: ftp signal=11 pid=3620 duration=0(sec) Before testing, I validated that nothing was using port 21 except for xinetd. If I retry another FTP straight after the initial failure, it works perfectly. I did some digging, and found a command line option in the proftpd man page that looked interesting... -N,--nocollision Disables address/port collision checking. I threw this into /etc/xinetd.d/proftpd and everything started working. Below is a copy of my file... I would appreciate it if a few of you could test this to verify it is indeed the smoking gun! Regards, Greg. ======= # default: off # $Id: proftpd-xinetd,v 1.2 2002/06/10 15:35:47 dude Exp $ # description: The ProFTPD FTP server serves FTP connections. It uses \ # normal, unencrypted usernames and passwords for authentication. service ftp { socket_type = stream wait = no user = root server = /usr/sbin/in.proftpd server_args = --nocollision log_on_success += DURATION log_on_failure += USERID nice = 10 disable = no instances = 80 } _______________________________________________ Blueonyx mailing list Blueonyx@mail.blueonyx.it http://mail.blueonyx.it/mailman/listinfo/blueonyx