• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Waiting for work units

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
I'm having the same problem of course. Getting error code 503 on every attempt to communicate with the Stanford servers. Did you guys know that when your computer isn't folding the CPU temp goes down? Crazy :rolleyes:

Code:
[19:39:53] + Attempting to send results
[19:39:53] Error: Got status code 503 from server
[19:39:53] + Could not connect to Work Server (results)
[19:39:53] - Error: Could not transmit unit 06 (completed January 18). Keeping unit in queue.
[19:58:03] + Attempting to get work packet
[19:58:03] - Connecting to assignment server
[19:58:13] - Successful: assigned to (171.64.122.119).
[19:58:13] + News From Folding@Home: Welcome to Folding@Home
[19:58:13] Loaded queue successfully.
[19:58:13] Error: Got status code 503 from server
[19:58:13] + Could not connect to Work Server
[19:58:13] - Error: Getwork #15 failed, and no other work to do. Waiting before retry
 
I finally got my farm back up in production, but my completed WU's are cached. All the new work came from server 108. Give it a try, 1 rig at a time.
 
muddocktor said:
I finally got my farm back up in production, but my completed WU's are cached. All the new work came from server 108. Give it a try, 1 rig at a time.

I got the one rig I had idle folding. The WU is still cached like you said. I'm not going to finish anymore work for about 2 hours. We shall see what happens then.
 
Yeah, I know what you mean. BTW, server 119 is back on line for sure, just sent in 5 WU's with the -send all switch. Also, the serverstats page is back up and it's showing server 109 to be up and running too. As always, YMMV.:)
 
Back