[SOLVED] Very Secure FTP (vsftpd) is refusing to start on Slackware Current
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Very Secure FTP (vsftpd) is refusing to start on Slackware Current
Hello Fellows,
I have had a fresh Slackware installation, in fact It's a Virtual box that I paid for..
The original installation came with Slackware 12.1 with the minimum requirements and I had to upgrade it to current, and install every thing I need, stating at get, slackpkg, which, and so on..!!
Any way, one of the many things I've installed was vsFTPD.
I tried to start it using the inted (the super server), and also in stand alone.. but it's not starting at all..
When I try to start it like:
Code:
root@slacky:/# vsftpd
It takes ages.. with no results, till I get to cancel by hitting CTRL+C.
Any idea what would be the problem?
I doubt that there are few needed libraries or something like that?
I googled.. but didn't get to any helpful results..
To let you know, I have tried all what you said earlier before I post this.
In fact, this is not the first time I install vsftpd.
I had installed and well configured on several other boxes, Slack and CentOS..
All works like charm.. only this one, something is not working..!!
Your welcome. Let's hope your problem is fixed.
I have some experience with ftp servers since I'm writing a FTP client program, and I had to set almost every open-source ftp servers to test my program.
Also as you probably imagine, making a ftp client program give me a lot of knolege on FTP.
I have to tell you I'm not familiarized with inetd and it's been a while since I use slack.
But I see two apparent problems in your configuration files if you want to work with inetd.
Change listen=YES to listen=NO.
Listen is used in standalone only, so if you want to test both standalone and inetd you have to disable listen.
Also I don't see an ftp line on inetd.conf
add to inetd.conf
Code:
# Very Secure File Transfer Protocol (FTP) server.
ftp stream tcp nowait root /usr/sbin/tcpd vsftpd
Also try to make vsftpd.conf very simple, so you can identify problems adding feature by feature.
But, I'm sorry to say, I guess you didn't understand my problem quite well.
I don't have problem into the way I use to start vsftpd..
I totally know, how to start it as a stand alone service, or via inetd.
So, the way to start it isn't the problem.
The problem, is the vsftp itself is refusing to start no matter how it was called..
When I type into the shell:
Code:
# vsftpd
I never got the command line back.. till I cancel the issued command.. (humm am I clear?)
So, what would be preventing vsftpd of being run?
a Socket?
a missed library?
a dependency?
Don't know.. that's what I'm trying to figure out..!!
Yeah, that's a pain in the neck, but it might give you a clue.
You don't need to understand much to benefit. You'll see lines like:
Code:
open("/etc/mtab", O_RDONLY) = 3
That's a succesful open. A failure looks like this:
Code:
open("/tmp/thingy", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
Pretty obvious, even if you didn't realize that the "-1" meant a problem.
Of course, the more you understand about system calls and programming, the more you can glean from strace output. If nothing else, you might spot where it is hanging/looping and posting that might give someone more familiar with its innards the needed clue.
I'm not going to read all that, but the "listen" is what it's supposed to do.
Did you look at netstat or lsof to see if it is listening for connections?
Did you try "ftp localhost" ?
I think I see your issue. You said "I never got the command line back.". Not all daemons fork themselves off - many expect to run in background - you'd do "vsftpd &" unless vsftpd is supposed to background itself.
.
I think I see your issue. You said "I never got the command line back.". Not all daemons fork themselves off - many expect to run in background - you'd do "vsftpd &" unless vsftpd is supposed to background itself.
.
You are going to laugh..
I figured that I solved this problem earlier by installing some needed packages.. or I think so..
Any way, I was trying the whole way to start vsftpd like:
Code:
~# vsftpd
I tried your hint to run it in the background..
to find out that it's already running..!!
Well, I guess some kind of miracles blessed the vsftpd and got it to work.. lol
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.