Start vsftpd with inetd

TheOther1 · 05-21-2003, 11:58 PM

Thanx, glad it worked.

perl -e 'print v78.111.116.32.121.101.116.32.97.32.80.101.114.108.32.104.97.99.107.101.114;'

bricklok · 05-22-2003, 10:34 PM

One more question... now I cant get inetd to load on boot up or when i just run it at CLI.... it doesnt give an error it just doesnt show up on processes and none of my inetd related servers work

thanks,

Phil

TheOther1 · 05-23-2003, 03:12 PM

It won't show unless the process is active, meaning there is an active FTP session. Check to make sure standalone = set to no.

FTP to the box then on the box, ps -aux | grep vsftpd

lrobert · 05-24-2003, 06:02 PM

Hi
i have the same problem error : 500 OOPS: could not bind listening socket and i haved followed your disscution and i want to ask lnxsdp what he exactily did when : "So I removed the portion to listen for ftp service from xinetd conf. directory "
Thanks

lsakhvoruk · 06-04-2003, 11:43 AM

Hi guys!

I am having an issue with vsftpd timing out in the middle of an upload. It usually times out after about 7.5 minutes.

I've increase both time out parameters to 10000 and it still does the same thing!

Any clues, leads, solutions will be greatly appreciated!

Thanks!

TheOther1 · 06-04-2003, 03:01 PM

Quote:

I am having an issue with vsftpd timing out in the middle of an upload. It usually times out after about 7.5 minutes.

Are you sure there is not cron job running that may kill you socket? I haven't had this problem, just throwing out an idea...

lsakhvoruk · 06-05-2003, 08:50 AM

Pretty sure there are no cron jobs running that would do that. I checked the messages log file and there are lots of lines like this
"vsftpd: warning: can't get client address: Bad file descriptor", not sure what that has to do with anything.

Thanks.

P.S. There is a hardware firewal and an antivirus appliance that connections go through before getting to the server. I set the firewal up myself and am pretty sure thats not the problem, but the appliance is a plug in and don't know whats happening situation (no set up).

TheOther1 · 06-05-2003, 04:34 PM

Quote:

"vsftpd: warning: can't get client address: Bad file descriptor", not sure what that has to do with anything.

That may be a DNS issue... Are you able to ping by name or perform dnslookups or digs on the box OK? I'm not sure if vsftpd tries to do a reverse lookup on connections or not. I don't think it does by default but if you are having general DNS issues, that may effect vsftpd.

dmx9595 · 07-03-2003, 02:16 PM

i didnt read all the posts so i dont know if ur problem got solved or not etc..
but i hade same problem with error
500 OOPS: could not bind listening socket
and changing LISTEN=YES to LISTEN=NO in my vsftpd.conf fixed it for me.

saavik · 07-02-2004, 02:54 AM

Hello!

I just had the same problem and found your conversation!!!

Thank you so much for your help, with which i just solved the problem!!!

bye!!

shimmer2101 · 07-02-2004, 08:01 AM

the bad file descriptor error is dns related.

i'm working on a box with no dns acces at all and i also get it, for most things i just use the /etc/hosts file but it seems vsftp doesn't use this.

my ftp works fine otherwise after botching my head for a day about the 500 oops error but it turned out i had some leftover ipchains rule.