- warning: "ProFTPD" address/port (10.0.5.1:21) already in use by "Debian"

[tom]

I don't understand this message:
- warning: "ProFTPD" address/port (10.0.5.1:21) already in use by "Debian"

In /etc/proftpd.conf

ServerName "Debian"

is defined. When I comment out ServerName:

#ServerName "Debian"

I get the message:
- warning: "ProFTPD" address/port (10.0.5.1:21) already in use by "ProFTPD"

Why I get that message?

tom

[till]

Please have a look here:

http://www.howtoforge.com/forums/sho...p?t=120&page=2

Please try to use the forum search function too This has been discussed several times already.

[tom]

Originally Posted by till

Please have a look here:

http://www.howtoforge.com/forums/sho...p?t=120&page=2

Please try to use the forum search function too This has been discussed several times already.

I was already been searching for this prob in this forum but I'm not using Suse, I'm using Debian3.1.
SocketBindTight on has'nt no effect in Debian3.1 and even an reboot.

tom

[falko]

Please put this at the end of /etc/proftpd.conf, right before "Include /etc/proftpd_ispconfig.conf":

<VirtualHost 127.0.0.1>
        DefaultRoot             ~
        AllowOverwrite          on
        Umask                   002
</VirtualHost>

Then restart proftpd.

[tom]

Originally Posted by falko

Please put this at the end of /etc/proftpd.conf, right before "Include /etc/proftpd_ispconfig.conf":

<VirtualHost 127.0.0.1>
        DefaultRoot             ~
        AllowOverwrite          on
        Umask                   002
</VirtualHost>

Then restart proftpd.

Ok, I've done it but in does'nt has any change in the start message.

tom

[falko]

Add a section like this for every IP address you have and restart proftpd.

[tom]

Originally Posted by falko

Add a section like this for every IP address you have and restart proftpd.

I've done that also but nothing changed.

tom

[falko]

If FTP is working nevertheless, I'd simply ignore the warning.

[tom]

Originally Posted by falko

If FTP is working nevertheless, I'd simply ignore the warning.

I've found that if I comment out this include in /etc/proftpd.conf
"#Include /etc/proftpd_ispconfig.conf"

the warning messege are gone.
But I don't understand why.

tom

[till]

The problem is that proftpd binds on the port before it reads the virtual server configuration. Thats a common problem and you can ignore it as falko posted.