Failed to start FTP server

12 posts / 0 new
Last post
#1 Fri, 06/03/2011 - 14:01
alexj1972

Failed to start FTP server

Hello everyone, today I was able to regain access via ssl to my webmin, thanks to the person who sold me the VPS, only that I no longer have access to FTP tells me it's down and I wrote this:

Failed to start FTP server: Starting ftp server: proftpd - Fatal: unknown configuration directive '/ ftp' ​​on line 93 of '/ etc / proftpd / modules.conf' failed!

This is the version of proftpd: ProFTPD Server ProFTPd version 1.33

I ask for help to restart ftp as it was yesterday.

Thanks to all for help

Fri, 06/03/2011 - 14:06
andreychek

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

Fri, 06/03/2011 - 14:20
alexj1972

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

Fri, 06/03/2011 - 14:27
andreychek

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 proftp

Fri, 06/03/2011 - 14:31
alexj1972

I run it as:

rpm-qa | grep proftp

from shell?

how?

Fri, 06/03/2011 - 14:34
andreychek

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

Fri, 06/03/2011 - 14:38
alexj1972

ok sent putty command: Reply

root @ alex: ~ # rpm-qa | grep proftp -bash: rpm: command not found root @ alex: ~ #

What does it mean?

Fri, 06/03/2011 - 14:42
andreychek

Hmm, which Linux distribution are you using?

-Eric

Fri, 06/03/2011 - 14:44
alexj1972

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

Fri, 06/03/2011 - 14:55
andreychek

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

Fri, 06/03/2011 - 15:16
alexj1972

ok after I put # in front gave me another error on line 93, put # in front and now everything ok.

by 1000

Fri, 06/03/2011 - 17:51
Locutus

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?

Topic locked