Unable to send finished wus

[miinkie]

Hi everyone .... been away for a while and on return i have 4 (on 3 rigs) instances of F@H that have been unable to send results. I have about 10 wus in queue but even turning off both router and software firewalls (temporarily to see if that was the problem) i still get errors like this:

[14:13:13] + Attempting to send results
[14:13:46] Couldn't send HTTP request to server (wininet)
[14:13:46] + Could not connect to Work Server (results)
[14:13:46] (171.65.103.160:8080)
[14:13:46] - Error: Could not transmit unit 08 (completed December 12) to work server.


[14:13:46] + Attempting to send results
[14:13:48] Error: Got status code 503 from server
[14:13:48] + Could not connect to Work Server (results)
[14:13:48] (171.65.103.100:8080)
[14:13:48] Could not transmit unit 08 to Collection server; keeping in queue.


[14:13:48] + Attempting to send results
[14:14:21] Couldn't send HTTP request to server (wininet)
[14:14:21] + Could not connect to Work Server (results)
[14:14:21] (171.64.122.128:8080)
[14:14:21] - Error: Could not transmit unit 09 (completed December 14) to work server

However looking at stats on extremeoverclocking (http://folding.extremeoverclocking.com/user_summary.php?s=&u=21822) i seem to be sending some results. Its happening on all my machines. Any suggestions would be greatly appreciated?

[csimon]

If it has sent wus before but not sending now then chances are the server at stanford is not currently accepting. You can check the server status at http://folding.stanford.edu

[miinkie]

Thanks for the prompt reply csimon. What is the 'error code 503'? Just curious

[csimon]

"10.5.4 503 Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.

Note: The existence of the 503 status code does not imply that a
server must use it when becoming overloaded. Some servers may wish
to simply refuse the connection."

It'll send eventually ...maybe early next week if not before the weekend.

[SPIKE09]

Hi if this isn't fixed the message wininet is probably due to the client setting "use ie settings" being set to yes , or from having IE7 installed it has been a common topic at the FCF. it would be well worthwhile running the -config flag to check the setting is at use ie setting's No and use proxy no. imho :buck: