I've been seeing quite a few odd log entries like this:

Jun 12 14:23:17 bleh proftpd[11826]: bleh.bleh.net - Failed binding to 0.0.0.0, port 21: Address already in use
Jun 12 14:34:18 bleh proftpd[11879]: bleh.bleh.net - Failed binding to 0.0.0.0, port 21: Address already in use
Jun 12 14:36:47 bleh proftpd[11895]: bleh.bleh.net - Failed binding to 0.0.0.0, port 21: Address already in use
Jun 12 15:19:20 bleh proftpd[14213]: bleh.bleh.net - Failed binding to 0.0.0.0, port 21: Address already in use
Jun 12 15:52:54 bleh proftpd[14531]: bleh.bleh.net - Failed binding to 0.0.0.0, port 21: Address already in use
Jun 12 15:58:39 bleh proftpd[14595]: bleh.bleh.net - Failed binding to 0.0.0.0, port 21: Address already in use
Jun 12 22:01:04 bleh proftpd[17696]: bleh.bleh.net - Failed binding to 0.0.0.0, port 21: Address already in use

The odd thing is that proftpd is configured standalone and there is no entry in inetd.conf! This makes little sense to me.

Anyone else had this problem?

check your /etc/proftp.conf file for duplicate entries of IP addresses and then restart proftpd or inetd.

Originally posted by Drewcifer
I've been seeing quite a few odd log entries like this:

The odd thing is that proftpd is configured standalone and there is no entry in inetd.conf! This makes little sense to me. If it is running in standalone mode, you shouldn't need an inetd.conf entry. If it was set to "inetd", then you would.

The ServerType directive configures the server daemon's operating mode. The type-identifier can be one of two values: inetd The daemon will expect to be run from the inetd "super server." New connections are passed from inetd to proftpd and serviced immediately. standalone The daemon starts and begins listening to the configured port for incoming connections. New connections result in spawned child processes dedicated to servicing all requests from the newly connected client.

That duplicate error could be the result of you (or something else) trying to start the server when it's already running. Try running /usr/sbin/proftpd as root and seeing if it produces the same errors in your log file.

also, make sure you don't have other ftp daemons running ( wu-ftpd, for example )