Printable View
Anyone else having problems.. I have a huge stash down here... nearly bursting at the seams.. well not really.. but it seems big and I get get any units uploaded :(
I can ping www.distributedfolding.org
and using tracert I get there in 21 hops
Any ideas ?
Odd. Mine are uploading just fine. Are you still having this problem?
Most definitely on 2 machines.. :(
Still can't upload them :(
This Sucks..
Anything useful in error.log? If not, what happens if you try to stop the client, move the directory over to another machine, and upload from there? (just use -ut in the foldit.bat/foldit batch/script file)
Contents of Error Log for today.
========================[ Mar 17, 2003 12:29 PM ]========================
ERROR: [000.000] {ncbi_http_connector.c, line 217} [HTTP] Error writing body at offset 8192
ERROR: [000.000] {ncbi_http_connector.c, line 117} [HTTP] Retry attempt(s) exhausted, giving up
ERROR: [000.000] {foldtrajlite.c, line 4397} Error during upload: NO RESPONSE FROM SERVER - WILL TRY AGAIN LATER
Can you telnet to www.distributedfolding.org port 80 from that machine?
Something like telnet www.distributedfolding.org 80 would accomplish that.
ping uses ICMP packets, and traceroute uses UDP packets, so there might be something with either TCP or TCP port 80 packets from that machine...
You're not using an HTTP proxy, are you?
HTTP/1.0 408 Request Time-out
Server: Squid/2.3.STABLE4
Mime-Version: 1.0
Date: Mon, 17 Mar 2003 11:41:07 GMT
Content-Type: text/html
Content-Length: 622
Expires: Mon, 17 Mar 2003 11:41:07 GMT
X-Squid-Error: ERR_LIFETIME_EXP 0
<HTML><HEAD>
<TITLE>ERROR: The requested URL could not be retrieved</TITLE>
</HEAD
><BODY>
<H1>ERROR</H1>
<H2>The requested URL could not be retrieved</H2>
<HR>
<P>
Whi
le trying to retrieve the URL:
<A HREF="N/A">N/A</A>
<P>
The following error was en
countered:
<UL>
<LI>
<STRONG>
Connection Lifetime Expired
</STRONG>
</UL>
<P>
Squid has
terminated the request because it has exceeded the maximum
connection lifetime.
<P
>Your cache administrator is <A HREF="mailto:webmaster">webmaster</A>.
<br clear
="all">
<hr noshade size=1>
Generated Mon, 17 Mar 2003 11:41:07 GMT by sprint-cach
e (Squid/2.3.STABLE4)
</BODY></HTML>
Connection to host lost.
D:\>
:(
That seems to be a known bug with certain HTTP proxies. The packets make their way to Howard's machine (and I don't remember for sure, but I think you still get credit for them), but the "received packet" HTTP reply (or whatever it's called; it's probably not "received packet") never makes it back.
No one can find the problem with the broken proxies, either. I've got a theory (and I just came up with it a minute ago, thinking about this) that perhaps the proxies are only optimized (or only work, period) with "normal" usage, which is downloading information using HTTP. It could be that uploading with HTTP is causing them to screw up.
In any case, you might contact your ISP (if this is an ISP's caching proxy; I noticed "sprint" in there, so that's why I assume it is) and see if there's any way to skip the proxy for DF. Maybe there's something you can set up so that packets miss the proxy, or maybe the ISP can make it so that your IP isn't forced through the proxy.
Or, if that's your own proxy, try disabling it and see if you can upload.
Save the following info into a file named proxy.cfg in the client dir:
I use this proxy with my Linux boxen as they won't upload work with my ISP's transparent proxy. It's a little slow, but it works.Code:195.205.230.210
8080
What does ERR_LIFETIME_EXP mean?
This means that a timeout occurred while the object was being transferred. Most likely the retrieval of this object was very slow (or it stalled before finishing) and the user aborted the request. However, depending on your settings for quick_abort, Squid may have continued to try retrieving the object. Squid imposes a maximum amount of time on all open sockets, so after some amount of time the stalled request was aborted and logged win an ERR_LIFETIME_EXP message.