On Friday 13 October 2006 01:19 pm, James G. Sack (jim) wrote:
> boblq wrote:

> Re diagnosing/debugging your problem:
>
> - When client 1 "hangs" -- does that mean it eventually succeeds after a
> delay (your 90 sec reference?)?

Yes it eventually succeeds. Something is definitely 
requiring a timeout before Client 1 can get to the
server. (Sure sounds like a hung socket to me.) 

> - What is your clients' & server environments?

environment? that can mean many things. Both 
clients are on Linux boxes on the same LAN 
behind a Linksys router and cable modem.

The server is a GoDaddy cheapo $3.98/month. 



> - Does the behavior change if you reverse the client roles? If you do
> both client steps from the same host?

Not sure. I don't have a good way to reverse the roles yet. The 
machine that has the pget.py does not have a browser. I suppose
I should move pget.py to a machine with a browser and try. That is
easy enough to do. 

OK. I brought the pget.py over to another local machine with 
a browser. It works fine. The browser does as well. No hang up.

But when I go to a third machine the broswer hangs  until the
90 sec timeout occurs. 

Conclusion, machines in my local network (don't know about
outsiders) are hung if the are different from the machine 
running the pget.py script. 

> - Do you have access to the server to do some poking around, or is it a
> limited-access hosted thingy? eg, can you monitor (via say netstat) the
> server end?

No access to the server ... but I could set up a server locally
and see what happens behind the Linksys router. 

> - Can the whole mess be run on another machine or set of machines?

I think I will try a local server first. That would be pretty
easy and let me look at both ends. Also it would take the
Internet and GoDaddy out of the picture. 

> - Can you substitute still another get-prog? perl (perl-libwww-perl) has
> a nice GET. Or lftpget (which has nice -v and -d options).

Well wget and Firefox seem enough to me. 

My workaround at the moment is to use wget inside Python
via an os.system() call. That works. I strongly suspect the 
that the Python urllib has some kind of a bug but don't
want to invest too much more in this now. Maybe later. 

BobLQ


> Regards,
> ..jim

-- 
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg

Reply via email to