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

Discussion in 'Installation/Configuration' started by tom, Apr 20, 2006.

  1. tom

    tom Member

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

    In /etc/proftpd.conf
    is defined. When I comment out ServerName:
    I get the message:
    - warning: "ProFTPD" address/port (10.0.5.1:21) already in use by "ProFTPD"

    Why I get that message?

    tom
     
    Last edited: Apr 21, 2006
  2. till

    till Super Moderator Staff Member ISPConfig Developer

  3. tom

    tom Member

    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
     
  4. falko

    falko Super Moderator Howtoforge Staff

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

    Code:
    <VirtualHost 127.0.0.1>
            DefaultRoot             ~
            AllowOverwrite          on
            Umask                   002
    </VirtualHost>
    Then restart proftpd.
     
  5. tom

    tom Member

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

    tom
     
  6. falko

    falko Super Moderator Howtoforge Staff

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

    tom Member

    I've done that also but nothing changed.

    tom
     
  8. falko

    falko Super Moderator Howtoforge Staff

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

    tom Member

    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
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    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.
     
  11. tom

    tom Member

    ok, I will leave it and believe... :)

    thanks
    tom
     

Share This Page