Folding Forum

Community driven support forum for Folding@home
https://foldingforum.org/

171.64.65.56 not responding

https://foldingforum.org/viewtopic.php?t=12022

Page 20 of 25

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 2:49 pm
by ikerekes
down again

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 4:09 pm
by JPinTO
Status 503
Could not connect to work server

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 4:26 pm
by Grandpa_01
So when they going to throw this puppy in the junk pile. I could use some parts and pieces. :mrgreen:

Code: Select all

[07:42:22] Completed 250000 out of 250000 steps  (100%)
[07:42:31] DynamicWrapper: Finished Work Unit: sleep=10000
[07:42:41] 
[07:42:41] Finished Work Unit:
[07:42:41] - Reading up to 21120768 from "work/wudata_01.trr": Read 21120768
[07:42:41] trr file hash check passed.
[07:42:41] - Reading up to 4445240 from "work/wudata_01.xtc": Read 4445240
[07:42:41] xtc file hash check passed.
[07:42:41] edr file hash check passed.
[07:42:41] logfile size: 192005
[07:42:41] Leaving Run
[07:42:41] - Writing 25908149 bytes of core data to disk...
[07:42:42]   ... Done.
[07:42:45] - Shutting down core
[07:42:45] 
[07:42:45] Folding@home Core Shutdown: FINISHED_UNIT
[07:46:02] CoreStatus = 64 (100)
[07:46:02] Sending work to server


[07:46:02] + Attempting to send results
[08:02:06] - Couldn't send HTTP request to server
[08:02:06] + Could not connect to Work Server (results)
[08:02:06]     (171.64.65.56:8080)
[08:02:06] - Error: Could not transmit unit 01 (completed November 1) to work server.
[08:02:06]   Keeping unit 01 in queue.


[08:02:06] + Attempting to send results
[08:18:11] - Couldn't send HTTP request to server
[08:18:11] + Could not connect to Work Server (results)
[08:18:11]     (171.64.65.56:8080)
[08:18:11] - Error: Could not transmit unit 01 (completed November 1) to work server.


[08:18:11] + Attempting to send results
[08:34:18] - Couldn't send HTTP request to server
[08:34:18] + Could not connect to Work Server (results)
[08:34:18]     (171.67.108.25:8080)
[08:34:18]   Could not transmit unit 01 to Collection server; keeping in queue.
[08:34:18] - Preparing to get new work unit...
[08:34:18] + Attempting to get work packet
[08:34:18] - Connecting to assignment server
[08:34:18] - Successful: assigned to (171.64.65.56).
[08:34:18] + News From Folding@Home: Welcome to Folding@Home
[08:34:18] Loaded queue successfully.
[08:34:18] - Couldn't send HTTP request to server
[08:34:18]   (Got status 503)
[08:34:18] + Could not connect to Work Server
[08:34:18] - Attempt #1  to get work failed, and no other work to do.
             Waiting before retry.
[08:34:32] + Attempting to get work packet
[08:34:32] - Connecting to assignment server
[08:34:32] - Successful: assigned to (171.64.65.56).
[08:34:32] + News From Folding@Home: Welcome to Folding@Home
[08:34:32] Loaded queue successfully.
[08:34:32] - Couldn't send HTTP request to server
[08:34:32]   (Got status 503)
[08:34:32] + Could not connect to Work Server
[08:34:32] - Attempt #2  to get work failed, and no other work to do.
             Waiting before retry.
[08:34:43] + Attempting to get work packet
[08:34:43] - Connecting to assignment server
[08:34:43] - Successful: assigned to (171.64.65.56).
[08:34:43] + News From Folding@Home: Welcome to Folding@Home
[08:34:43] Loaded queue successfully.
[08:34:43] - Couldn't send HTTP request to server
[08:34:43]   (Got status 503)
[08:34:43] + Could not connect to Work Server
[08:34:43] - Attempt #3  to get work failed, and no other work to do.
             Waiting before retry.
[08:35:08] + Attempting to get work packet
[08:35:08] - Connecting to assignment server
[08:35:08] - Successful: assigned to (171.64.65.56).
[08:35:08] + News From Folding@Home: Welcome to Folding@Home
[08:35:08] Loaded queue successfully.
[08:35:08] - Couldn't send HTTP request to server
[08:35:08]   (Got status 503)
[08:35:08] + Could not connect to Work Server
[08:35:08] - Attempt #4  to get work failed, and no other work to do.
             Waiting before retry.
[08:35:59] + Attempting to get work packet
[08:35:59] - Connecting to assignment server
[08:35:59] - Successful: assigned to (171.64.65.56).
[08:35:59] + News From Folding@Home: Welcome to Folding@Home
[08:35:59] Loaded queue successfully.
[08:35:59] - Couldn't send HTTP request to server
[08:35:59]   (Got status 503)
[08:35:59] + Could not connect to Work Server
[08:35:59] - Attempt #5  to get work failed, and no other work to do.
             Waiting before retry.
[08:37:29] + Attempting to get work packet
[08:37:29] - Connecting to assignment server
[08:37:29] - Successful: assigned to (171.64.65.56).
[08:37:29] + News From Folding@Home: Welcome to Folding@Home
[08:37:29] Loaded queue successfully.
[08:37:29] - Couldn't send HTTP request to server
[08:37:29]   (Got status 503)
[08:37:29] + Could not connect to Work Server
[08:37:29] - Attempt #6  to get work failed, and no other work to do.
             Waiting before retry.
[08:40:15] + Attempting to get work packet
[08:40:15] - Connecting to assignment server
[08:40:16] - Successful: assigned to (171.64.65.56).
[08:40:16] + News From Folding@Home: Welcome to Folding@Home
[08:40:16] Loaded queue successfully.
[08:40:16] - Couldn't send HTTP request to server
[08:40:16]   (Got status 503)
[08:40:16] + Could not connect to Work Server
[08:40:16] - Attempt #7  to get work failed, and no other work to do.
             Waiting before retry.
[08:45:36] + Attempting to get work packet
[08:45:36] - Connecting to assignment server
[08:45:36] - Successful: assigned to (171.64.65.56).
[08:45:36] + News From Folding@Home: Welcome to Folding@Home
[08:45:36] Loaded queue successfully.
[08:45:36] - Couldn't send HTTP request to server
[08:45:36]   (Got status 503)
[08:45:36] + Could not connect to Work Server
[08:45:36] - Attempt #8  to get work failed, and no other work to do.
             Waiting before retry.
[08:56:30] + Attempting to get work packet
[08:56:30] - Connecting to assignment server
[08:56:30] - Successful: assigned to (171.64.65.56).
[08:56:30] + News From Folding@Home: Welcome to Folding@Home
[08:56:30] Loaded queue successfully.
[08:56:30] - Couldn't send HTTP request to server
[08:56:30]   (Got status 503)
[08:56:30] + Could not connect to Work Server
[08:56:30] - Attempt #9  to get work failed, and no other work to do.
             Waiting before retry.

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 5:14 pm
by slugbug
Both of my SMP folders are currently waiting for work from the assignment server 171.64.65.56

Code: Select all

[12:19:55] - Attempt #8  to get work failed, and no other work to do.
             Waiting before retry.
[12:30:38] + Attempting to get work packet
[12:30:38] - Connecting to assignment server
[12:30:39] - Successful: assigned to (171.64.65.56).
[12:30:39] + News From Folding@Home: Welcome to Folding@Home
[12:30:39] Loaded queue successfully.
[12:30:39] - Couldn't send HTTP request to server
[12:30:39]   (Got status 503)
[12:30:39] + Could not connect to Work Server
[12:30:39] - Attempt #9  to get work failed, and no other work to do.
             Waiting before retry.
[12:52:11] + Attempting to get work packet
[12:52:11] - Connecting to assignment server
[12:52:12] - Successful: assigned to (171.64.65.56).
[12:52:12] + News From Folding@Home: Welcome to Folding@Home
[12:52:12] Loaded queue successfully.
[12:52:12] - Couldn't send HTTP request to server
[12:52:12]   (Got status 503)
[12:52:12] + Could not connect to Work Server
[12:52:12] - Attempt #10  to get work failed, and no other work to do.
             Waiting before retry.

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 5:39 pm
by theo343
Netload on 171.64.65.56 is at 200

Same problem here on 4 of my Linux SMP folders. Tried to restart them but no luck.

I tried to turn off advmethods aswell and reboot to get another WU server, but didnt help.

Code: Select all

[18:29:39] [18:24:23] - Attempt #7  to get work failed, and no other work to do.
             Waiting before retry.
[18:29:52] + Attempting to get work packet
[18:29:52] - Connecting to assignment server
[18:29:53] - Successful: assigned to (171.64.65.56).
[18:29:53] + News From Folding@Home: Welcome to Folding@Home
[18:29:53] Loaded queue successfully.
[18:29:53] - Couldn't send HTTP request to server
[18:29:53]   (Got status 503)
[18:29:53] + Could not connect to Work Server
[18:29:53] - Attempt #8  to get work failed, and no other work to do.
             Waiting before retry.

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 6:42 pm
by preet.to
Cannot send or receive on all of mine. Been this way most of the day. One by one all production is halting for me.

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 6:50 pm
by bruce
Grandpa_01 wrote:So when they going to throw this puppy in the junk pile. I could use some parts and pieces. :mrgreen:
You don't REALLY want them to shut down this server yet. They need to wait until the new hardware is ready to replace it. See the News for Oct 13

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 7:17 pm
by Grandpa_01
Yep I read that a while back. I was hopeing they had recieved them and were replacing them today. I currentley have 7 clients down both GPU and SMP within the next 7hrs 14 clients will be down. Hopefully something will be resolved before then.

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 8:15 pm
by bruce
There are two initiatives going on and their interactions may cause delays. (1) New hardware, and (2) New server code. With issues like this, it's not always clear (to me, at least) whether the primary issue is related to hardware or software. The ultimate solution is to do both upgrades, but that means the old servers probably have to hold out longer that you expect. (I don't set the priorities and I don't have a detailed roadmap.)

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 8:37 pm
by theo343
Why doesnt the clients get rerouted to another WU server like 171.64.65.63 or 64?

http://fah-web.stanford.edu/localinfo/contact.SMP.html

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 9:00 pm
by road-runner
Mine sent in a result but cant get anymore work on the big wus...

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 9:14 pm
by toTOW
theo343 wrote:Why doesnt the clients get rerouted to another WU server like 171.64.65.63 or 64?
Because the AS doesn't know when a server is overloaded network side ... it only knows when a server is offline or out of work :(

Some people in my team reported that they got A1 work after restarting the client ...

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 9:44 pm
by weedacres
toTOW wrote:
theo343 wrote:
Some people in my team reported that they got A1 work after restarting the client ...
I had the same problem.

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 9:53 pm
by theo343
Now all my local clients seems to be folding again. There are two clients i cant check until tomorrow.

Re: 171.64.65.56 not responding

Posted: Sun Nov 01, 2009 10:44 pm
by road-runner
Mine finally got a 2662 a2 at least...
All times are UTC
Page 20 of 25

Powered by phpBB® Forum Software © phpBB Limited