RE: Timeout While Retrieving Directory Listing

Well, for some strange reason it now works!  The only action I took in =
between the tests before I sent the last email and this one was =
rebooting my local machine and restarting pure-ftpd on the server. =20

Very strange.  Unfortunately I wasn't logging anything from pure-ftpd, =
so I'm not sure what might have occurred differently.

At this point, I'm just going to cross my fingers and hope it continues =
to work.

Again, thanks for your help.

--Jason

-----Original Message-----
From: DervishD [mailto:[email protected]]=20
Sent: Thursday, January 19, 2006 10:35 AM
To: Whaley, Jason
Cc: [email protected]
Subject: Re: [pureftpd] Timeout While Retrieving Directory Listing

    Hi Jason :)

 * Whaley, Jason <[email protected]> dixit:
> I disabled passive connections in Filezilla (my test ftp client),
> and I am receiving the same timeout.

    My problem was not with passive connections, but with *extended*
passive connections. Anyway, this problem doesn't seem to be related
with that.
=20
> I used ftp from the command line from my work machine and I could
> connect and be placed in the chroot'ed directory for the ftp user.=20
> However, an issuance of dir or ls takes 60 seconds exactly
> everytime to complete from the command line ftp, but does work.=20
> The behavior of ls and dir is that the output is shown, but hangs
> for 60 seconds, then the report is shown.

    I had exactly the same problem with the default ftp server (I
don't remember which one) under SuSE five years ago. I don't remember
if I finally solved it.

> Could this be a port issue when connecting from a client?  It seems
> to me it may be something network related since ftp'ing from
> localhost works flawlessly.

    You have to make sure that you're using the correct range of
ports for passive mode (the same that your OS says you can use. Under
Linux, you can find those under /proc/sys/net/ipv4/ip_local_port_range).

    I must confess that I'm completely lost with your problem. If I
were you, I would try, in this order:

    - Try a few ftp clients. Some of them are extremely dumb and may
need workarounds in the server (since fixing proprietary clients is
impossible).

    - Try another ftp server in the machine to see if the problem is
pure-ftpd's fault or network's fault.

    - Try a precompiled version (or a prepackaged one, if you happen
to be using a distribution instead of a DIY box).

    - Locate where the heck the server is spending those 60 seconds
(or the client, if the delay is client's fault).

    - Sniff the network traffic when the delay occurs, just to make
sure the problem is not an obvious one (cabling, devices, etc.).

    If other ftp servers work OK, then the problem is related to
pureftpd (at least partially) and then you should try to track down
where the server is sleeping, or use the other ftp server if time is
an issue.

    If you want me to try your server, just tell. On the other hand,
if you need to test your clients against a working pureftpd, just
tell me and I'll give you a disposable account in my pureftpd so you
can test if the problem exists too.

    Ra=FAl N=FA=F1ez de Arenas Coronado

--=20
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...



---------------------------------------------------------------------
To post a new message, e-mail: [email protected]
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]