[11:51:51] - Ask before connecting: No
[11:51:51] - User name: gangster911 (Team 90478)
[11:51:51] - User ID: 44B52D4A0808E60D
[11:51:51] - Machine ID: 1
[11:51:51]
[11:51:51] Work directory not found. Creating...
[11:51:51] Could not open work queue, generating new queue...
[11:51:51] Initialization complete
[11:51:51] - Preparing to get new work unit...
[11:51:51] + Attempting to get work packet
[11:51:51] - Connecting to assignment server
[11:52:13] - Couldn't send HTTP request to server
[11:52:13] + Could not connect to Assignment Server
[11:52:16] - Successful: assigned to (171.64.122.72).
[11:52:16] + News From Folding@Home: Welcome to Folding@Home
[11:52:16] Loaded queue successfully.
[11:52:18] - Couldn't send HTTP request to server
[11:52:18] (Got status 501)
[11:52:18] + Could not connect to Work Server
[11:52:18] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[11:52:25] + Attempting to get work packet
[11:52:25] - Connecting to assignment server
[11:52:47] - Couldn't send HTTP request to server
[11:52:47] + Could not connect to Assignment Server
[11:52:49] - Successful: assigned to (171.64.122.72).
[11:52:49] + News From Folding@Home: Welcome to Folding@Home
[11:52:49] Loaded queue successfully.
[11:52:49] - Couldn't send HTTP request to server
[11:52:49] (Got status 501)
[11:52:49] + Could not connect to Work Server
[11:52:49] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[11:53:08] + Attempting to get work packet
[11:53:08] - Connecting to assignment server
[11:53:30] - Couldn't send HTTP request to server
[11:53:30] + Could not connect to Assignment Server
[11:53:33] - Successful: assigned to (171.64.122.72).
[11:53:33] + News From Folding@Home: Welcome to Folding@Home
[11:53:33] Loaded queue successfully.
[11:53:34] - Couldn't send HTTP request to server
[11:53:34] (Got status 501)
[11:53:34] + Could not connect to Work Server
[11:53:34] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[11:53:58] + Attempting to get work packet
[11:53:58] - Connecting to assignment server
[11:54:20] - Couldn't send HTTP request to server
[11:54:20] + Could not connect to Assignment Server
[11:54:22] - Successful: assigned to (171.64.122.72).
[11:54:22] + News From Folding@Home: Welcome to Folding@Home
[11:54:22] Loaded queue successfully.
[11:54:22] - Couldn't send HTTP request to server
[11:54:22] (Got status 501)
[11:54:22] + Could not connect to Work Server
[11:54:22] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
You're getting assigned to a uniprocessor server ...
Error 501 means "Not implemented" ... I don't know what functionality you request is not implemented, but I've never seen this error code before on FAH servers
Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
gangster911 wrote:9 views..
no reply..
-.-
sigh...
Welcome to the forum.
You aren't being ignored, you just asked an unusual question. I also have never seen "Got status 501" either, so I am not qualified to give any kind of helpful answer.
A quick search of this forum and of the FaHWiki also didn't show any results.
It is the weekend now, but someone who does know should be along shortly that can give you a meaningful answer and hopefully help with your problem.
More details of your machine, network connection, what OS (Vista maybe?) and what client you're using would help.
The server you're trying to conect to is up, but busy (according to the status page).
What proxy settings are you using? Do you connect through a proxy? What kind of security software are you running?
You do need to tell us which client and which OS you're running.
The fact that nobody else is reporting problems with this server tends to indicate that the problem is closer to your machine than to Stanford, but we won't really know until we get enough information to figure it out.
Executable: FAH6.exe
Arguments: -local -verbosity 9 -send 4
[23:30:30] - Ask before connecting: No
[23:30:30] - User name: xxxxxx (Team 0)
[23:30:30] - User ID: xxxxxxxxxxx
[23:30:30] - Machine ID: 2
[23:30:30]
[23:30:31] Loaded queue successfully.
[23:30:31] Attempting to return result(s) to server...
[23:30:31] Project: 4419 (Run 11, Clone 19, Gen 129)
[23:30:31] - Read packet limit of 540015616... Set to 524286976.
[23:30:31] + Attempting to send results [November 24 23:30:31 UTC]
[23:30:31] - Reading file work/wuresults_04.dat from core
[23:30:31] (Read 592278 bytes from disk)
[23:30:31] Connecting to http://171.64.122.72:8080/
[23:33:38] - Couldn't send HTTP request to server
[23:33:38] + Could not connect to Work Server (results)
[23:33:38] (171.64.122.72:8080)
[23:33:38] + Retrying using alternative port
[23:33:38] Connecting to http://171.64.122.72:80/
[23:36:34] - Couldn't send HTTP request to server
[23:36:34] + Could not connect to Work Server (results)
[23:36:34] (171.64.122.72:80)
[23:36:34] - Error: Could not transmit unit 04 (completed November 11) to work server.
[23:36:34] - 36 failed uploads of this unit.
[23:36:34] - Read packet limit of 540015616... Set to 524286976.
[23:36:34] + Attempting to send results [November 24 23:36:34 UTC]
[23:36:34] - Reading file work/wuresults_04.dat from core
[23:36:34] (Read 592278 bytes from disk)
[23:36:34] Connecting to http://171.67.108.17:8080/
[23:36:34] - Couldn't send HTTP request to server
[23:36:34] (Got status 503)
[23:36:34] + Could not connect to Work Server (results)
[23:36:34] (171.67.108.17:8080)
[23:36:34] + Retrying using alternative port
[23:36:34] Connecting to http://171.67.108.17:80/
[23:36:34] - Couldn't send HTTP request to server
[23:36:34] (Got status 503)
[23:36:34] + Could not connect to Work Server (results)
[23:36:34] (171.67.108.17:80)
[23:36:34] Could not transmit unit 04 to Collection server; keeping in queue.
[23:36:34] - Failed to send unit 04 to server
[23:36:34] ***** Got a SIGTERM signal (2)
[23:36:34] Killing all core threads
Folding@Home Client Shutdown.
I have 7 WUs waiting to go to this server for a couple of weeks.
There is little doubt in my mind that the server at 171.64.122.72 is overloaded. It is issuing a large percentage of the new WUs for the CPU client and several of the other uniprocessor servers are pretty busy, too. Some new projects are being prepared for the CPU client but they still need so testing before they're ready to be released.
As far as uploads are concerned, the Collection Servers are also very heavily loaded.
The Pande Group is aware of both problems. Some progress is being made, but I can't give you any estimate when either problem will be fully resolved.
