These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Failed to start FTP server on the new forum.
Web Hosting and Cloud Computing Control Panels
It sounds like something is wrong with line 93 of the config file "/etc/proftpd/modules.conf". Which is unusual, as that should work by default.
However, what I'd do is try commenting that line out, then restart ProFTPd, and see if that resolves the issue.
-Eric
hello, I did as you said but I always write this error:
Executing / etc / init.d / proftpd restart ..
Stopping ftp server: proftpd. Starting ftp server: proftpd - Fatal: unknown configuration directive '/ ftp' on line 93 of '/ etc / proftpd / modules.conf' failed!
This is the script runs proftpd FTP Service Offered
how can I fix without reinstalling everything ftp?
thanks
Well, that's a different line number... you could try commenting out that one too.
However, I'm curious... what is the output of this command:
rpm -qa | grep proftpI run it as:
rpm-qa | grep proftp
from shell?
how?
The command is "rpm -qa | grep proftp" -- you would indeed run that from the shell, by first logging in as root via SSH. You would have to use a SSH client for that, such as Putty.
-Eric
ok sent putty command: Reply
root @ alex: ~ # rpm-qa | grep proftp -bash: rpm: command not found root @ alex: ~ #
What does it mean?
Hmm, which Linux distribution are you using?
-Eric
System hostname alex Operating system Debian Linux 6.0 Webmin version 1.550 Time on system Fri Jun 3 19:44:12 2011 Kernel and CPU Linux 2.6.32-5-amd64 on x86_64 Processor information Intel(R) Xeon(R) CPU L5410 @ 2.33GHz, 4 cores System uptime 11 hours, 32 minutes Running processes 102 CPU load averages 0.00 (1 min) 0.00 (5 mins) 0.00 (15 mins) CPU usage 0% user, 0% kernel, 0% IO, 100% idle Real memory 1.96 GB total, 113.76 MB used
Virtual memory 2 GB total, 0 bytes used
Local disk space 78.74 GB total, 5.68 GB used
Package updates 7 package updates are available
Ah, for some reason I was assuming you were using CentOS.
Debian 6 normally works out of the box, so something unusual is going on :-)
Re-reading your two error messages, I just realized that was the same line number each time.
Are you sure you commented out line 93?
What you'd need to do is edit "/etc/proftpd/modules.conf", go to line 93, and put a "#" mark before whatever content exists on that line.
-Eric
ok after I put # in front gave me another error on line 93, put # in front and now everything ok.
by 1000
I'm not sure if simply commenting out config lines that obviously contain errors is the right way to go.
This kinda reminds me of Portal 2 which I recently played, where the character Wheatley "fixed" the problem of impending reactor core meltdown by disabling the alert system. ;)
What about uploading the config file instead to pastebin.com so we can take a look at it?