Page 1 of 1

Doesn't get work packet - 503 error

Posted: Mon Dec 22, 2008 2:18 pm
by Igloo
14:04:20] - Ask before connecting: No
[14:04:20] - User name: ^Igloo^ (Team 35947)
[14:04:20] - User ID: 7DE52AF31A54F176
[14:04:20] - Machine ID: 2
[14:04:20]
[14:04:20] Loaded queue successfully.
[14:04:20] Initialization complete
[14:04:20] - Preparing to get new work unit...
[14:04:20] + Attempting to get work packet
[14:04:20] - Connecting to assignment server
[14:04:21] - Successful: assigned to (171.64.65.106).
[14:04:21] + News From Folding@Home: GPU folding beta
[14:04:22] Loaded queue successfully.
[14:04:22] - Couldn't send HTTP request to server
[14:04:22] (Got status 503)
[14:04:22] + Could not connect to Work Server
[14:04:22] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[14:04:34] + Attempting to get work packet
[14:04:34] - Connecting to assignment server
[14:04:35] - Successful: assigned to (171.64.65.106).
[14:04:35] + News From Folding@Home: GPU folding beta
[14:04:35] Loaded queue successfully.
[14:04:35] - Couldn't send HTTP request to server
[14:04:35] (Got status 503)
[14:04:35] + Could not connect to Work Server
[14:04:35] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[14:04:56] + Attempting to get work packet
[14:04:56] - Connecting to assignment server
[14:04:57] - Successful: assigned to (171.64.65.106).
[14:04:57] + News From Folding@Home: GPU folding beta
[14:04:58] Loaded queue successfully.
[14:04:58] - Couldn't send HTTP request to server
[14:04:58] (Got status 503)
[14:04:58] + Could not connect to Work Server



This has just been installed. Though the hardware has been running for a long time under xp.

Re: Doesn't get work packet - 503 error

Posted: Mon Dec 22, 2008 2:23 pm
by Igloo
This has now got a work unit.

[14:16:14] + Attempting to get work packet
[14:16:14] - Connecting to assignment server
[14:16:16] - Successful: assigned to (171.64.65.106).
[14:16:16] + News From Folding@Home: GPU folding beta
[14:16:16] Loaded queue successfully.
[14:16:29] + Closed connections
[14:16:29]
[14:16:29] + Processing work unit

Strange how it wasn't working before, Server glitch or high load?

Re: Doesn't get work packet - 503 error

Posted: Mon Dec 22, 2008 2:45 pm
by Hazzard
im not getting any either.

[14:36:42] + Attempting to get work packet
[14:36:42] - Connecting to assignment server
[14:36:43] - Successful: assigned to (171.64.65.106).
[14:36:43] + News From Folding@Home: GPU folding beta
[14:36:43] Loaded queue successfully.
[14:36:43] - Couldn't send HTTP request to server
[14:36:43] (Got status 503)
[14:36:43] + Could not connect to Work Server
[14:36:43] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.

Re: Doesn't get work packet - 503 error

Posted: Mon Dec 22, 2008 2:51 pm
by Igloo
I'm going to go with high load for that server...

Maybe one of the folding staff can look at that server :)

Re: Doesn't get work packet - 503 error

Posted: Mon Dec 22, 2008 3:45 pm
by slugbug

Code: Select all

[14:45:21] + Attempting to send results [December 22 14:45:21 UTC]
[14:45:21] - Couldn't send HTTP request to server
[14:45:21]   (Got status 503)
[14:45:21] + Could not connect to Work Server (results)
[14:45:21]     (171.67.108.25:8080)
[14:45:21] + Retrying using alternative port
[14:45:22] - Couldn't send HTTP request to server
[14:45:22]   (Got status 503)
[14:45:22] + Could not connect to Work Server (results)
[14:45:22]     (171.67.108.25:80)
[14:45:22]   Could not transmit unit 05 to Collection server; keeping in queue.
[15:10:07] + Attempting to get work packet
[15:10:07] - Connecting to assignment server
[15:10:08] - Successful: assigned to (171.67.108.11).
[15:10:08] + News From Folding@Home: GPU folding beta
[15:10:08] Loaded queue successfully.
[15:10:08] + Could not connect to Work Server
[15:10:08] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.

Re: Doesn't get work packet - 503 error

Posted: Mon Dec 22, 2008 3:47 pm
by slugbug
Getting the same thing with 171.67.108.25

Code: Select all

[14:45:21] + Attempting to send results [December 22 14:45:21 UTC]
[14:45:21] - Couldn't send HTTP request to server
[14:45:21]   (Got status 503)
[14:45:21] + Could not connect to Work Server (results)
[14:45:21]     (171.67.108.25:8080)
[14:45:21] + Retrying using alternative port
[14:45:22] - Couldn't send HTTP request to server
[14:45:22]   (Got status 503)
[14:45:22] + Could not connect to Work Server (results)
[14:45:22]     (171.67.108.25:80)
[14:45:22]   Could not transmit unit 05 to Collection server; keeping in queue.
[15:10:07] + Attempting to get work packet
[15:10:07] - Connecting to assignment server
[15:10:08] - Successful: assigned to (171.67.108.11).
[15:10:08] + News From Folding@Home: GPU folding beta
[15:10:08] Loaded queue successfully.
[15:10:08] + Could not connect to Work Server
[15:10:08] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.

Re: Doesn't get work packet - 503 error

Posted: Mon Dec 22, 2008 11:08 pm
by bruce
Status 503 does mean high load.
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.

Re: Doesn't get work packet - 503 error

Posted: Tue Dec 23, 2008 10:43 am
by Igloo
Surely "Temporary Overloading" = high load? :)

Re: Doesn't get work packet - 503 error

Posted: Tue Dec 23, 2008 6:40 pm
by bruce
Igloo wrote:Surely "Temporary Overloading" = high load? :)
The message for 503 uses the words Temporary Overloading, but when a server is seeing high load, there's no way to know how long that condition will persist. I, for one, am glad the error 503 is issued rather than the more meaningless message "Couldn't send HTTP request to server"

Re: Doesn't get work packet - 503 error

Posted: Sun Jan 04, 2009 5:44 am
by kremechoco
Perhaps the server is loaded with workgiving?