Very Secure FTP (vsftpd) is refusing to start on Slackware Current
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:
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..
Thanks in advance..!!
Don't forget to configure first
At first, Thanks a lot for replying..
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..!!
Please post the your vsftpd.conf and inetd.conf
Also have a look on my previous thread responses to vsftpd.
Here they are:
I have mostly enabled every thing in vsftpd.conf trying to figure out the problem:
Here is inetd.conf, I tried to start vsftpd from inted, and as stand alone.. neither worked..
By the way, thanks for your other replies (the ones you pointed to)
I had a look on them, I don't think they solve my problem..
I repeat my thanks.. :)
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
Try this only as your vsftpd.conf:
This will test your vsftpd trough inetd
To test standalone
comment comment the ftp line on inetd.conf
ammorais, I repeat my thanks..
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:
So, what would be preventing vsftpd of being run?
a missed library?
Don't know.. that's what I'm trying to figure out..!!
Trace it with "strace"
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:
That's a succesful open. A failure looks like this:
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.
Alright, here you are..
To be honest, I couldn't derive the failure reason.. as I'm not too geek :$ !!
Dose it show you something?
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 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:
to find out that it's already running..!!
Well, I guess some kind of miracles blessed the vsftpd and got it to work.. lol
Don't ask me how, I don't know :p
You deserved a Thump Up :-)
Regards all ..
Late, I know.
Also, don't forget to check your /etc/hosts.allow and /etc/hosts.deny files for host access controls
|All times are GMT -5. The time now is 12:15 AM.|