I am having serious problems with ProFTPd Version 1.2.10 and ISPconfig Version: 2.1.2 on Mandriva 2005 LE. I can't seem to get proftpd started in my server. here is my config and the errors I am getting. I have tried searching for a solution for this in this section of the forum but I don't get an answer that works. Code: ServerName "Webenergy.ca FTP" ServerType standalone DefaultServer on AllowStoreRestart on Port 21 Umask 022 MaxInstances 30 # Set the user and group under which the server will run. User nobody Group nogroup DefaultRoot ~ AllowOverwrite on <Limit SITE_CHMOD> DenyAll </Limit> PersistentPasswd off <Global> AllowOverwrite on </Global> DisplayGoAway "Too Many Connections. Try Later." DisplayLogin "Login Successful" DisplayQuit "Goodbye" <Anonymous ~hockeypool> User ftp Group nogroup UserAlias hockeypool ftp HideNoAccess on <Limit LOGIN> Allow All </Limit> <Limit ALL> Deny All </Limit> <Limit PWD CWD LIST RETR> Allow ALL </Limit> <Directory /home/hockeypool> Umask 022 022 <Limit MKD STOR> Allow All </Limit> </Directory> </Anonymous> Include /etc/proftpd_ispconfig.conf ################################### # # ISPConfig proftpd Configuration File # Version 1.0 # ################################### <VirtualHost 192.168.1.100> DefaultRoot ~ AllowOverwrite on Umask 002 </VirtualHost> <VirtualHost 192.168.1.101> DefaultRoot ~ AllowOverwrite on Umask 002 </VirtualHost> This is my syslog results Code: Apr 16 20:13:54 webenegy proftpd: proftpd shutdown succeeded Apr 16 20:13:54 webenegy proftpd[10147]: webenergy.ca - notice: 'Webenergy.ca FTP' (192.168.1.100:21) already bound to 'Webenergy.ca FTP' Apr 16 20:13:54 webenegy proftpd[10147]: webenergy.ca - bindings.c:913: notice: unable to create ipbind '192.168.1.100': Address already in use Apr 16 20:13:54 webenegy proftpd[10147]: webenergy.ca - ProFTPD 1.2.10 (stable) (built Mon Aug 15 12:35:14 MDT 2005) standalone mode STARTUP Apr 16 20:13:54 webenegy proftpd[10147]: webenergy.ca - listen() failed in inet_listen(): Address already in use Apr 16 20:13:54 webenegy proftpd: proftpd startup succeeded Apr 16 20:14:27 webenegy proftpd: proftpd shutdown failed Apr 16 20:14:27 webenegy proftpd[10324]: webenergy.ca - notice: 'Webenergy.ca FTP' (192.168.1.100:21) already bound to 'Webenergy.ca FTP' Apr 16 20:14:27 webenegy proftpd[10324]: webenergy.ca - bindings.c:913: notice: unable to create ipbind '192.168.1.100': Address already in use Apr 16 20:14:27 webenegy proftpd[10324]: webenergy.ca - ProFTPD 1.2.10 (stable) (built Mon Aug 15 12:35:14 MDT 2005) standalone mode STARTUP Apr 16 20:14:27 webenegy proftpd[10324]: webenergy.ca - listen() failed in inet_listen(): Address already in use Apr 16 20:14:27 webenegy proftpd: proftpd startup succeeded Please help. I have checked all my firewall rules and I can't figure out why this is not working. I think it started to fail after I did a ISPConfig update and then just recently an init 6 reboot, then the errors started to show up.
<Limit LOGIN> Allow All </Limit> <Limit ALL> Deny All </Limit> <Limit PWD CWD LIST RETR> Allow ALL Thats interesting and you;re address is already being used by ISPConfig, you just need to allow the permissions /etc/proftpd_[IP_ADDRESS].conf <--- adds the included file. http://www.howtoforge.com/forums/showthread.php?t=518 And dont give aways so much info, it leaves you open to be brute forced...
I took out all of the above The permissions are the exact same as the proftpd.conf. And there is no proftpd_[IP_ADDRESS].conf file in the /etc dir.
Yes, I added the directive ... Code: SocketBindTight on to the proftpd.conf file. I am beginning to think this might be a DNS issue or soemthing else other than ISPConfig settings.... Hmmmmm. any ideas of where to check?
Solution? Im not sure if ISPConfig had anything at all to do with proftpd running or not. This is what I recently did and how I think things might have gotten fixed. Before I noticed that PROFTPD was running I ... I cleanned up my /ETC/HOSTS file. I didn't have 127.0.0.1 defined as localhost I don't thing this is what fixed it, but who knows???After this I restarted SYSLOGD the daemon. I had not restarted the daemon since fixing a typo in my /ETC/HOSTS file about a month ago. I think there might have been and DNS conflict when PROFTPD tried to start and there was no setting in the hosts file for the domain in memory Hope this helps anyone. ALSO, THANKS YOU FALCO for being patient with me...! I LOVE ISPCONFIG!