Jump to content
caintry_boy

Stanford Down...

Recommended Posts

There was just a problem with points submitting on Feb. 1

As for point updates, it does that every 3 hours to add up the points you've made in that time frame.

The update times are 3, 6, 9 and 12.

Share this post


Link to post
Share on other sites

Wth, I just posted points @the 3pm reporting time but have been folding the whole time.

Share this post


Link to post
Share on other sites

There was no data reporting since 9pm yesterday. Stanford may be down or experiencing an error on their site.

 

Although the error may affect the accessibility of the Stanford site, it does not affect the ability to send and receive work units.

Edited by EclipseWebJS2

Share this post


Link to post
Share on other sites

Stanford down again? Some problem with points?

Just curious as I'm noticing the team seems to have hardly any points submitted for yesterday. As well as for today I have not yet received any points for wu that finished some time this morning.

Share this post


Link to post
Share on other sites

Justin check out the Chimp Challenge threads and you will know were a lot of us are folding. Stanford's servers appear to be fine.

Share this post


Link to post
Share on other sites
[17:30:23] Folding@home Core Shutdown: FINISHED_UNIT[17:30:27] CoreStatus = 64 (100)[17:30:27] Unit 5 finished with 80 percent of time to deadline remaining.[17:30:27] Updated performance fraction: 0.801078[17:30:27] Sending work to server[17:30:27] Project: 10090 (Run 29, Clone 3, Gen 54)[17:30:27] + Attempting to send results [April 14 17:30:27 UTC][17:30:27] - Reading file work/wuresults_05.dat from core[17:30:27]   (Read 1562371 bytes from disk)[17:30:27] Connecting to http://129.74.85.15:8080/[17:30:29] Posted data.[17:30:29] Initial: 0000; - Uploaded at ~763 kB/s[17:30:29] - Averaged speed for that direction ~533 kB/s[17:30:29] + Results successfully sent[17:30:29] Thank you for your contribution to Folding@Home.

Well it shows to have finished and submitted just fine in FAHlog. That was at 17:30 UTC (I have no clue what time that is USA on central time). But I got no points at either 3pm or 6pm updates. I know it was done by 3pm here on account I seen the new wu already started. Well, I was just curious though.

Share this post


Link to post
Share on other sites

Yes, just checked the client config settings file and it shows username, team # and passkey as it should. :shrug:

Share this post


Link to post
Share on other sites

There must have just been a delay somewhere along the line. I received credit as of the 3am update.

Share this post


Link to post
Share on other sites

You should know --

 

During the Chimp Challenge folding race, you can remove delays by switching your team number to 32.

 

-- It's true! <well, it could happen, but it's fun, anyway, and we really need some help>

Share this post


Link to post
Share on other sites

Looks like the place is going down...

04:11:13:WU04:FS00:Sending unit results: id:04 state:SEND error:FAULTY project:8900 run:14 clone:7 gen:264 core:0x17 unit:0x00000157028c1266519a62454ccd3a9104:11:13:WU04:FS00:Uploading 3.50KiB to 171.64.65.6904:11:13:WU04:FS00:Connecting to 171.64.65.69:808004:11:34:ERROR:WU00:FS02:Exception: Failed to connect to 171.65.103.160:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:11:34:WARNING:WU04:FS00:WorkServer connection failed on port 8080 trying 8004:11:34:WU04:FS00:Connecting to 171.64.65.69:8004:11:41:WU01:FS02:Connecting to assign3.stanford.edu:808004:11:44:WU03:FS00:Connecting to assign-GPU.stanford.edu:8004:11:55:WARNING:WU04:FS00:Exception: Failed to send results to work server: Failed to connect to 171.64.65.69:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:11:55:WU04:FS00:Trying to send results to collection server04:11:55:WU04:FS00:Uploading 3.50KiB to 171.65.103.16004:11:55:WU04:FS00:Connecting to 171.65.103.160:808004:12:02:WARNING:WU01:FS02:Failed to get assignment from 'assign3.stanford.edu:8080': Failed to connect to assign3.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:12:02:WU01:FS02:Connecting to assign4.stanford.edu:8004:12:05:WARNING:WU03:FS00:Failed to get assignment from 'assign-GPU.stanford.edu:80': Failed to connect to assign-GPU.stanford.edu:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:12:05:WU03:FS00:Connecting to assign-GPU.stanford.edu:808004:12:16:WARNING:WU04:FS00:WorkServer connection failed on port 8080 trying 8004:12:16:WU04:FS00:Connecting to 171.65.103.160:8004:12:23:WARNING:WU01:FS02:Failed to get assignment from 'assign4.stanford.edu:80': Failed to connect to assign4.stanford.edu:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:12:23:ERROR:WU01:FS02:Exception: Could not get an assignment04:12:26:WARNING:WU03:FS00:Failed to get assignment from 'assign-GPU.stanford.edu:8080': Failed to connect to assign-GPU.stanford.edu:8080: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:12:26:ERROR:WU03:FS00:Exception: Could not get an assignment04:12:37:ERROR:WU04:FS00:Exception: Failed to connect to 171.65.103.160:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:12:47:WU00:FS02:Sending unit results: id:00 state:SEND error:NO_ERROR project:9005 run:26 clone:0 gen:0 core:0xa4 unit:0x00000000664f2de452b801833553393f04:12:47:WU00:FS02:Uploading 1.57MiB to 171.64.65.12404:12:47:WU00:FS02:Connecting to 171.64.65.124:808004:12:50:WU04:FS00:Sending unit results: id:04 state:SEND error:FAULTY project:8900 run:14 clone:7 gen:264 core:0x17 unit:0x00000157028c1266519a62454ccd3a9104:12:50:WU04:FS00:Uploading 3.50KiB to 171.64.65.6904:12:50:WU04:FS00:Connecting to 171.64.65.69:808004:13:08:WARNING:WU00:FS02:WorkServer connection failed on port 8080 trying 8004:13:08:WU00:FS02:Connecting to 171.64.65.124:8004:13:11:WARNING:WU04:FS00:WorkServer connection failed on port 8080 trying 8004:13:11:WU04:FS00:Connecting to 171.64.65.69:8004:13:29:WARNING:WU00:FS02:Exception: Failed to send results to work server: Failed to connect to 171.64.65.124:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:13:29:WU00:FS02:Trying to send results to collection server04:13:29:WU00:FS02:Uploading 1.57MiB to 171.65.103.16004:13:29:WU00:FS02:Connecting to 171.65.103.160:808004:13:32:WARNING:WU04:FS00:Exception: Failed to send results to work server: Failed to connect to 171.64.65.69:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:13:32:WU04:FS00:Trying to send results to collection server04:13:32:WU04:FS00:Uploading 3.50KiB to 171.65.103.16004:13:32:WU04:FS00:Connecting to 171.65.103.160:808004:13:36:FS00:Finishing04:13:40:FS02:Finishing04:13:50:WARNING:WU00:FS02:WorkServer connection failed on port 8080 trying 8004:13:50:WU00:FS02:Connecting to 171.65.103.160:8004:13:52:FS00:Paused04:13:53:WARNING:WU04:FS00:WorkServer connection failed on port 8080 trying 8004:13:53:WU04:FS00:Connecting to 171.65.103.160:8004:13:57:FS02:Paused04:14:11:ERROR:WU00:FS02:Exception: Failed to connect to 171.65.103.160:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:14:14:ERROR:WU04:FS00:Exception: Failed to connect to 171.65.103.160:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:15:27:WU04:FS00:Sending unit results: id:04 state:SEND error:FAULTY project:8900 run:14 clone:7 gen:264 core:0x17 unit:0x00000157028c1266519a62454ccd3a9104:15:27:WU04:FS00:Uploading 3.50KiB to 171.64.65.6904:15:27:WU04:FS00:Connecting to 171.64.65.69:808004:15:48:WARNING:WU04:FS00:WorkServer connection failed on port 8080 trying 8004:15:48:WU04:FS00:Connecting to 171.64.65.69:8004:16:09:WARNING:WU04:FS00:Exception: Failed to send results to work server: Failed to connect to 171.64.65.69:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:16:09:WU04:FS00:Trying to send results to collection server04:16:09:WU04:FS00:Uploading 3.50KiB to 171.65.103.16004:16:09:WU04:FS00:Connecting to 171.65.103.160:808004:16:30:WARNING:WU04:FS00:WorkServer connection failed on port 8080 trying 8004:16:30:WU04:FS00:Connecting to 171.65.103.160:8004:16:51:ERROR:WU04:FS00:Exception: Failed to connect to 171.65.103.160:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:17:01:WU00:FS02:Sending unit results: id:00 state:SEND error:NO_ERROR project:9005 run:26 clone:0 gen:0 core:0xa4 unit:0x00000000664f2de452b801833553393f04:17:01:WU00:FS02:Uploading 1.57MiB to 171.64.65.12404:17:01:WU00:FS02:Connecting to 171.64.65.124:808004:17:22:WARNING:WU00:FS02:WorkServer connection failed on port 8080 trying 8004:17:22:WU00:FS02:Connecting to 171.64.65.124:8004:17:43:WARNING:WU00:FS02:Exception: Failed to send results to work server: Failed to connect to 171.64.65.124:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:17:43:WU00:FS02:Trying to send results to collection server04:17:43:WU00:FS02:Uploading 1.57MiB to 171.65.103.16004:17:43:WU00:FS02:Connecting to 171.65.103.160:808004:18:04:WARNING:WU00:FS02:WorkServer connection failed on port 8080 trying 8004:18:04:WU00:FS02:Connecting to 171.65.103.160:8004:18:25:ERROR:WU00:FS02:Exception: Failed to connect to 171.65.103.160:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:19:41:WU04:FS00:Sending unit results: id:04 state:SEND error:FAULTY project:8900 run:14 clone:7 gen:264 core:0x17 unit:0x00000157028c1266519a62454ccd3a9104:19:41:WU04:FS00:Uploading 3.50KiB to 171.64.65.6904:19:41:WU04:FS00:Connecting to 171.64.65.69:808004:19:44:WU02:FS01:0x17:Completed 225000 out of 2500000 steps (9%)04:20:02:WARNING:WU04:FS00:WorkServer connection failed on port 8080 trying 8004:20:02:WU04:FS00:Connecting to 171.64.65.69:8004:20:23:WARNING:WU04:FS00:Exception: Failed to send results to work server: Failed to connect to 171.64.65.69:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:20:23:WU04:FS00:Trying to send results to collection server04:20:24:WU04:FS00:Uploading 3.50KiB to 171.65.103.16004:20:24:WU04:FS00:Connecting to 171.65.103.160:808004:20:45:WARNING:WU04:FS00:WorkServer connection failed on port 8080 trying 8004:20:45:WU04:FS00:Connecting to 171.65.103.160:8004:21:06:ERROR:WU04:FS00:Exception: Failed to connect to 171.65.103.160:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:23:52:WU00:FS02:Sending unit results: id:00 state:SEND error:NO_ERROR project:9005 run:26 clone:0 gen:0 core:0xa4 unit:0x00000000664f2de452b801833553393f04:23:52:WU00:FS02:Uploading 1.57MiB to 171.64.65.12404:23:52:WU00:FS02:Connecting to 171.64.65.124:808004:24:13:WARNING:WU00:FS02:WorkServer connection failed on port 8080 trying 8004:24:13:WU00:FS02:Connecting to 171.64.65.124:8004:24:34:WARNING:WU00:FS02:Exception: Failed to send results to work server: Failed to connect to 171.64.65.124:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:24:34:WU00:FS02:Trying to send results to collection server04:24:35:WU00:FS02:Uploading 1.57MiB to 171.65.103.16004:24:35:WU00:FS02:Connecting to 171.65.103.160:808004:24:56:WARNING:WU00:FS02:WorkServer connection failed on port 8080 trying 8004:24:56:WU00:FS02:Connecting to 171.65.103.160:8004:25:17:ERROR:WU00:FS02:Exception: Failed to connect to 171.65.103.160:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:26:32:WU04:FS00:Sending unit results: id:04 state:SEND error:FAULTY project:8900 run:14 clone:7 gen:264 core:0x17 unit:0x00000157028c1266519a62454ccd3a9104:26:33:WU04:FS00:Uploading 3.50KiB to 171.64.65.6904:26:33:WU04:FS00:Connecting to 171.64.65.69:808004:26:54:WARNING:WU04:FS00:WorkServer connection failed on port 8080 trying 8004:26:54:WU04:FS00:Connecting to 171.64.65.69:8004:27:15:WARNING:WU04:FS00:Exception: Failed to send results to work server: Failed to connect to 171.64.65.69:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.04:27:15:WU04:FS00:Trying to send results to collection server04:27:15:WU04:FS00:Uploading 3.50KiB to 171.65.103.16004:27:15:WU04:FS00:Connecting to 171.65.103.160:808004:27:36:WARNING:WU04:FS00:WorkServer connection failed on port 8080 trying 8004:27:36:WU04:FS00:Connecting to 171.65.103.160:8004:27:57:ERROR:WU04:FS00:Exception: Failed to connect to 171.65.103.160:80: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Doesn't look good...I have one vid card client and a cpu down without work. When the last vid card fails I'm shutting down till after Christmas, .....maybe.

 

 

 

 

:geezer:

Share this post


Link to post
Share on other sites

Well, mine are all back up and running, BUT! there are several people including Uncle Fuzzy over at Stanford who responded to the threads that I started there on server issues. They are not happy campers, but at least Stanford will be aware that there is a problem. Hope no one else has problems as there appear to be several servers malfunctioning. :pullhair:

 

Fold On people!

 

 

 

 

:geezer:

Share this post


Link to post
Share on other sites

Stanford has a long track record of "going down" during the holidays when there is no body to respond to or repair as they are not there.

 

Merry Christmas to All! :xmas_biggrin:

Share this post


Link to post
Share on other sites

You might have seen a few zeroes with work units turned in, that's because there were problems with work units I had and the FAHClient spit it out of my computer.

Share this post


Link to post
Share on other sites

You might have seen a few zeroes with work units turned in, that's because there were problems with work units I had and the FAHClient spit it out of my computer.

 

See the snippet of log I posted above. The servers weren't responding, they were down so, yes, we got zeroes cause we had no work. Lucky for me it was fairly short lived...

 

 

 

 

:geezer:

Share this post


Link to post
Share on other sites

Well, once again they're down and contrary to Prof. Pande no one has gotten them up and running again yet today... Yes I realize it's only 10:45 am in Cali but C'Mon guys!!

 

:pullhair:

 

 

 

 

:geezer:

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×