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 21 of 25

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 12:04 am
by Pick2
I would have been here, because I had some blades out of work/finish WU not sending , but We had a power outage for hours right after this started :(
Count your blessings :P :lol:

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 3:08 am
by Grandpa_01
She's having problems again. I have 3 waiting to send / recieve.

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 3:10 am
by uncle fuzzy
I had 3 VM SMPs go idle trying to upload over the past 24 hours. A reset, one at a time. took care of that.

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 3:18 am
by road-runner
I guess it is out of big WUs all I am getting is the small ones...

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 3:25 am
by weedacres
Down again, can't upload or download.

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 3:28 am
by Grandpa_01
Hey uncle fuzzy it worked but I got a1 WU's instead of a2's

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 5:22 am
by uncle fuzzy
With more reports of trouble, I just checked all the machines. Nothing needs the server for another 3 hours, but I did find one of the VMs running at 76 PPD. It would finish in 18 days 19 hours. Oops. Now I have to stay up to make sure the reset "took".

2 others had been idle for 4-6 hours today waiting to upload.

Re: 171.64.65.56 is in Reject status

Posted: Mon Nov 02, 2009 5:32 am
by Ragnar Dan

Code: Select all

[01:26:14] - Preparing to get new work unit...
[01:26:14] + Attempting to get work packet
[01:26:14] - Connecting to assignment server
[01:26:14] - Successful: assigned to (171.64.65.56).
[01:26:14] + News From Folding@Home: Welcome to Folding@Home
[01:26:14] Loaded queue successfully.
[01:26:15] - Couldn't send HTTP request to server
[01:26:15]   (Got status 503)
[01:26:15] + Could not connect to Work Server
[01:26:15] - Attempt #1  to get work failed, and no other work to do.
             Waiting before retry.
[05:26:32] + Attempting to get work packet
[05:26:32] - Connecting to assignment server
[05:26:33] - Successful: assigned to (171.64.65.56).
[05:26:33] + News From Folding@Home: Welcome to Folding@Home
[05:26:33] Loaded queue successfully.
[05:26:33] - Couldn't send HTTP request to server
[05:26:33]   (Got status 503)
[05:26:33] + Could not connect to Work Server
[05:26:33] - Attempt #2  to get work failed, and no other work to do.
             Waiting before retry.
[05:26:55] + Attempting to get work packet
[05:26:55] - Connecting to assignment server
[05:26:55] - Successful: assigned to (171.64.65.56).
[05:26:55] + News From Folding@Home: Welcome to Folding@Home
[05:26:56] Loaded queue successfully.
[05:26:56] - Couldn't send HTTP request to server
[05:26:56]   (Got status 503)
[05:26:56] + Could not connect to Work Server
[05:26:56] - Attempt #3  to get work failed, and no other work to do.
             Waiting before retry.
[05:27:18] + Attempting to get work packet
[05:27:18] - Connecting to assignment server
[05:27:18] - Successful: assigned to (171.64.65.56).
[05:27:18] + News From Folding@Home: Welcome to Folding@Home
[05:27:18] Loaded queue successfully.
[05:27:19] - Couldn't send HTTP request to server
[05:27:19]   (Got status 503)
[05:27:19] + Could not connect to Work Server
[05:27:19] - Attempt #4  to get work failed, and no other work to do.
             Waiting before retry.
[05:28:06] + Attempting to get work packet
[05:28:06] - Connecting to assignment server
[05:28:06] - Successful: assigned to (171.64.65.56).
[05:28:06] + News From Folding@Home: Welcome to Folding@Home
[05:28:07] Loaded queue successfully.
[05:28:07] - Couldn't send HTTP request to server
[05:28:07]   (Got status 503)
[05:28:07] + Could not connect to Work Server
[05:28:07] - Attempt #5  to get work failed, and no other work to do.
             Waiting before retry.
[05:29:33] + Attempting to get work packet
[05:29:33] - Connecting to assignment server
[05:29:33] - Successful: assigned to (171.64.65.56).
[05:29:33] + News From Folding@Home: Welcome to Folding@Home
[05:29:33] Loaded queue successfully.
[05:29:33] - Couldn't send HTTP request to server
[05:29:33]   (Got status 503)
[05:29:33] + Could not connect to Work Server
[05:29:33] - Attempt #6  to get work failed, and no other work to do.
             Waiting before retry.
[05:32:24] + Attempting to get work packet
[05:32:24] - Connecting to assignment server
[05:32:24] - Successful: assigned to (171.64.65.56).
[05:32:24] + News From Folding@Home: Welcome to Folding@Home
[05:32:24] Loaded queue successfully.
[05:32:24] - Couldn't send HTTP request to server
[05:32:24]   (Got status 503)
[05:32:24] + Could not connect to Work Server
[05:32:24] - Attempt #7  to get work failed, and no other work to do.
             Waiting before retry.
I'm not sure now long that's beeen going on, because the system it's on has become somewhat unreliable, but anyway, I can't get a WU for it. (The time change is the system sync-ing after a reset.)

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 7:47 am
by k1wi
Got another Linux VM work unit waiting to connect to this server.

Code: Select all

[07:19:56] + Attempting to get work packet
[07:19:56] - Will indicate memory of 1112 MB
[07:19:56] - Connecting to assignment server
[07:19:56] Connecting to http://assign.stanford.edu:8080/
[07:19:57] Posted data.
[07:19:57] Initial: 40AB; - Successful: assigned to (171.64.65.56).
[07:19:57] + News From Folding@Home: Welcome to Folding@Home
[07:19:58] Loaded queue successfully.
[07:19:58] Connecting to http://171.64.65.56:8080/
[07:19:58] - Couldn't send HTTP request to server
[07:19:58]   (Got status 503)
[07:19:58] + Could not connect to Work Server
[07:19:58] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.
Took about 20 retries for my other two earlier in the day. I hope all is okay!

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 8:19 am
by theo343
Now I can't send results to this server. I also tried resetting all folders again now but didnt help.
[08:10:24] + Attempting to send results [November 2 08:10:24 UTC]
[08:10:24] - Couldn't send HTTP request to server
[08:10:24] (Got status 503)
[08:10:24] + Could not connect to Work Server (results)
[08:10:24] (171.64.65.56:8080)
[08:10:24] + Retrying using alternative port
[08:10:25] - Couldn't send HTTP request to server
[08:10:25] (Got status 503)
[08:10:25] + Could not connect to Work Server (results)
[08:10:25] (171.64.65.56:80)
[08:10:25] - Error: Could not transmit unit 07 (completed November 2) to work server.

[08:10:25] + Attempting to send results [November 2 08:10:25 UTC]
I guess most big-folders are using Linux SMP and this must be frustrating for a lot of them. Im used to problems doing FAH but networking overloads are the most frustrating onces since they can be easily avoided and isnt a coding problem.

Have you ever thought about setting up proxy WU servers instead of having all the network and data transfer load to one location? You should seriously think about setting up a proxy oriented model of the WU servers. I guess this can be accomplished by renting resources on servercenters around the world. There should be a proxy on each continent for each type of client. These proxies are the ones who in a timly manner should send clientresults back to you, get new bulks of WUs and assign them to the clients.

Right now your model are too vunerable and you should start thinking of branching out.

I hope Stanford can give us an updated ETA on the operational status of the new servers. (still no proxy oriented model, but at least an improvement)

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 12:39 pm
by Grandpa_01
Well it's Monday morning and I see we are still having problems I have 5 waiting and 1 got lucky and got a WU around 1AM. I think I will shut down for a while until this problem can be fixed it is a little costly to leave these machines running to do nothing.

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 1:03 pm
by toTOW
Morning, morning ... it's 5am at Stanford :roll:

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 1:06 pm
by frag85
guess this was the wrong weekend to return to folding. i was hoping this new 4.2ghz i7 would beat out my old 3.7ghz P4 northwood.

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 1:10 pm
by uncle fuzzy
I had 1 go idle overnight. I reset the VM and got a new WU, but I'm still waiting to see if it uploads the last one. It's been a half hour, so I'm not real hopeful.

Re: 171.64.65.56 not responding

Posted: Mon Nov 02, 2009 1:21 pm
by Grandpa_01
Whats your secret uncle fuzzy, I have reset my machines multiple times, the only WU's I get are a1's which I shouldn't be getting they don't run very well on notfreds. All that I have been doing is trashing a1 WU which just delays there completion.
All times are UTC
Page 21 of 25

Powered by phpBB® Forum Software © phpBB Limited