Page 22 of 28

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Sun Feb 21, 2010 7:17 pm
by Teddy
I finally restarted & was bumped to 20 for a new unit & the old protein was sent off OK.
This pausing of the client just sitting there doing nothing is really annoying..

Teddy

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Sun Feb 21, 2010 8:50 pm
by noorman
.

If your Client were to pause again after a "successful send", try and stop it, then deleting the Work folder and the queue.dat file.
Then restart ...

The Client should then run as mine does; it sends back the Results, downloads another WU and starts Folding again ...
( last time this happened, finishing, sending back, downloading and starting again took 7 seconds (broadband highspeed Internet connection)
[21:43:39] - Shutting down core
[21:43:39]
[21:43:39] Folding@home Core Shutdown: FINISHED_UNIT
[21:43:42] CoreStatus = 64 (100)
[21:43:42] Unit 4 finished with 97 percent of time to deadline remaining.
[21:43:42] Updated performance fraction: 0.974998
[21:43:42] Sending work to server
[21:43:42] Project: 5910 (Run 14, Clone 138, Gen 4)


[21:43:42] + Attempting to send results [February 21 21:43:42 UTC]
[21:43:42] - Reading file work/wuresults_04.dat from core
[21:43:42] (Read 44079 bytes from disk)
[21:43:42] Connecting to http://171.64.65.20:8080/
[21:43:44] Posted data.
[21:43:44] Initial: 0000; - Uploaded at ~22 kB/s
[21:43:44] - Averaged speed for that direction ~43 kB/s
[21:43:44] + Results successfully sent
[21:43:44] Thank you for your contribution to Folding@Home.
[21:43:44] + Number of Units Completed: 2925

[21:43:48] Trying to send all finished work units
[21:43:48] + No unsent completed units remaining.
[21:43:48] - Preparing to get new work unit...
[21:43:48] + Attempting to get work packet
[21:43:48] - Will indicate memory of 2046 MB
[21:43:48] - Connecting to assignment server
[21:43:48] Connecting to http://assign-GPU.stanford.edu:8080/
[21:43:49] Posted data.
[21:43:49] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[21:43:49] + News From Folding@Home: Welcome to Folding@Home
[21:43:49] Loaded queue successfully.
[21:43:49] Connecting to http://171.64.65.71:8080/
[21:43:50] Posted data.
[21:43:50] Initial: 0000; - Receiving payload (expected size: 89145)
[21:43:51] - Downloaded at ~87 kB/s
[21:43:51] - Averaged speed for that direction ~72 kB/s
[21:43:51] + Received work.
[21:43:51] Trying to send all finished work units
[21:43:51] + No unsent completed units remaining.
[21:43:51] + Closed connections
[21:43:51]
[21:43:51] + Processing work unit
[21:43:51] Core required: FahCore_11.exe
[21:43:51] Core found.
[21:43:51] Working on queue slot 05 [February 21 21:43:51 UTC]
[21:43:51] + Working ...
.

This one took 9 secs ...


.

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Sun Feb 21, 2010 11:44 pm
by BuddhaChu
Pile another one on for 171.64.65.71

Code: Select all

[23:36:48] + Attempting to send results [February 21 23:36:48 UTC]
[23:36:48] - Connecting to assignment server
[23:36:48] - Successful: assigned to (171.64.65.71).
[23:36:48] + News From Folding@Home: Welcome to Folding@Home
[23:36:49] Loaded queue successfully.
[23:36:49] - Couldn't send HTTP request to server
[23:36:49] + Could not connect to Work Server
[23:36:49] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[23:36:49] - Server does not have record of this unit. Will try again later.
[23:36:49] - Error: Could not transmit unit 01 (completed February 21) to work server.
EDIT: I quit the client and played a game for a while and the server was acting nicer later (accepting WUs).

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 12:26 am
by VijayPande
ok, we'll continue to investigate this. Joe has been working on the CS the last few days, and that is still having some problems (but he has ideas). This is all due to the shaking out of the v5 server code which apparently had some bugs hiding. As I've mentioned in previous posts, I have also dramatically slowed down the new WS rollouts to avoid these sorts of QA disasters in the future.

For now, just so we can understand the problem, could you confirm that the problem you're seeing is just with 171.64.65.71 or is it with other servers?

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 12:36 am
by bollix47
In my case I have only seen it happen today on 171.64.65.71 and it's happened at least twice with the message "Server does not have record of this unit. Will try again later." on two separate clients and two different computers. After trying port 8080 twice on the WS the client tried 171.67.108.26 and that's where the 'hang' occurs. After a restart of the client the WU uploaded immediately to the WS.

Here's the link to my previous post with the log of one of the failed attempts for reference:

viewtopic.php?p=132475#p132475

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 2:20 am
by noorman
.

On my rig, when it downloaded from 171.64.65.71, it always seems to upload to 171.67.108.26 without a problem (only a retry or 2 at max.)

No problems - here - with other servers either ...


.

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 6:35 am
by BuddhaChu
Sorry, I can't give more adequate feedback than what I posted above as I start/stopped the client so many times the logs are a mess and not easy to follow.

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 12:43 pm
by DavidMudkips
noorman wrote:
Have you checked if these gave a "succesfully sent" and "thank you ..." from the server ?
That might be the cause of that message ... (as told before)
Why the Client would still be re-trying, I don't know.

Best to check the log(s) for that all-telling info on these WU's (results)

.
No such messages were given. Here's my last error message, from the 16th. The others were from the initial outage on the 14th, and they didn't have successfully sent messages either.

Code: Select all

[23:21:43] + Attempting to send results [February 16 23:21:43 UTC]
[23:21:43] - Reading file work/wuresults_02.dat from core
[23:21:43]   (Read 132407 bytes from disk)
[23:21:43] Connecting to http://171.64.65.71:8080/
[23:30:10] Posted data.
[23:40:40] - Autosending finished units... [February 16 23:40:40 UTC]
[23:40:40] Trying to send all finished work units
[23:40:40] - Already sending work
[23:40:40] + Sent 0 of 1 completed units to the server
[23:40:40] - Autosend completed
[23:50:10] Initial: 00FA; - Uploaded at ~0 kB/s
[23:57:28] - Averaged speed for that direction ~29 kB/s
[23:57:28] - Unknown packet returned from server, expected ACK for results
[23:57:28] - Error: Could not transmit unit 02 (completed February 16) to work server.
[23:57:28] - 1 failed uploads of this unit.
[23:57:28]   Keeping unit 02 in queue.
[23:57:28] Trying to send all finished work units
[23:57:28] Project: 10102 (Run 87, Clone 9, Gen 10)
[23:57:28] - Read packet limit of 540015616... Set to 524286976.


[23:57:28] + Attempting to send results [February 16 23:57:28 UTC]
[23:57:28] - Reading file work/wuresults_02.dat from core
[23:57:28]   (Read 132407 bytes from disk)
[23:57:28] Connecting to http://171.64.65.71:8080/
[23:57:51] Posted data.
[23:57:51] Initial: 0000; - Uploaded at ~5 kB/s
[23:57:51] - Averaged speed for that direction ~24 kB/s
[23:57:51] - Server has already received unit.
[23:57:51] + Sent 0 of 1 completed units to the server
[23:57:51] - Preparing to get new work unit...

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 1:18 pm
by noorman
VijayPande wrote:ok, we'll continue to investigate this. Joe has been working on the CS the last few days, and that is still having some problems (but he has ideas). This is all due to the shaking out of the v5 server code which apparently had some bugs hiding. As I've mentioned in previous posts, I have also dramatically slowed down the new WS rollouts to avoid these sorts of QA disasters in the future.

For now, just so we can understand the problem, could you confirm that the problem you're seeing is just with 171.64.65.71 or is it with other servers?
.

Odd, since my system can connect (all of the time) with 171.64.65.71 ...

Code: Select all

[04:08:39] Shutting down core 
[04:08:39] 
[04:08:39] Folding@home Core Shutdown: FINISHED_UNIT
[04:08:42] CoreStatus = 64 (100)
[04:08:42] Unit 7 finished with 96 percent of time to deadline remaining.
[04:08:42] Updated performance fraction: 0.972671
[04:08:42] Sending work to server
[04:08:42] Project: 10105 (Run 117, Clone 0, Gen 9)


[04:08:42] + Attempting to send results [February 22 04:08:42 UTC]
[04:08:42] - Reading file work/wuresults_07.dat from core
[04:08:42]   (Read 132213 bytes from disk)
[04:08:42] Connecting to http://171.64.65.71:8080/
[04:08:44] Posted data.
[04:08:44] Initial: 0000; - Uploaded at ~65 kB/s
[04:08:44] - Averaged speed for that direction ~46 kB/s
[04:08:44] + Results successfully sent
[04:08:44] Thank you for your contribution to Folding@Home.
[04:08:44] + Number of Units Completed: 2928

[04:08:48] Trying to send all finished work units
[04:08:48] + No unsent completed units remaining.
[04:08:48] - Preparing to get new work unit...
[04:08:48] + Attempting to get work packet
[04:08:48] - Will indicate memory of 2046 MB
[04:08:48] - Connecting to assignment server
[04:08:48] Connecting to http://assign-GPU.stanford.edu:8080/
[04:08:49] Posted data.
[04:08:49] Initial: 40AB; - Successful: assigned to (171.64.65.20).
[04:08:49] + News From Folding@Home: Welcome to Folding@Home
[04:08:49] Loaded queue successfully.
[04:08:49] Connecting to http://171.64.65.20:8080/
[04:08:50] Posted data.
[04:08:50] Initial: 0000; - Receiving payload (expected size: 69013)
[04:08:51] - Downloaded at ~67 kB/s
[04:08:51] - Averaged speed for that direction ~74 kB/s
[04:08:51] + Received work.
[04:08:51] Trying to send all finished work units
[04:08:51] + No unsent completed units remaining.
[04:08:51] + Closed connections
.

EDIT: It does download work from it, but sends back Results to 171.67.108.26, not the source (171.64.65.71)

.

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 3:30 pm
by weedacres
noorman wrote: Odd, since my system can connect (all of the time) with 171.64.65.71 ...
.
My experience too. I checked 10 gpu clients, 5 have been doing business with 171.64.65.71 over the last few days and none had any problem.

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 5:59 pm
by bruce
noorman wrote:Odd, since my system can connect (all of the time) with 171.64.65.71 ...

. . .

EDIT: It does download work from it, but sends back Results to 171.67.108.26, not the source (171.64.65.71)
The last post that I saw from Dr. Pande said they though they had the problem fixed but they were waiting to see what happened, so there are probably some loose ends to clean up.

171.64.65.71 is a Work Server. 171.67.108.26 is a Collection Server. Collection Servers are supposed to upload results when Work Servers cannot accept them.

I don't know if this is true, but it is a reasonable theory which fits the facts that we can see. As the fix was being developed, a huge backlog of unuploaded WUs has built up. If there's a way to temporarily disable uploads on the Work Server until the crisis has passed and let it keep assigning new work while the CS accepts the uploads, it would be an effective way to deal with the overload they've been seeing. Once the crisis has passed and the number of connections has returned to normal, it could be re-enabled. Even without the backlog, it's also possible that the fix is being rolled out gradually. With a redundant path for uploading, they could have fixed one path first and could be waiting to see if everything works before applying the fix to another server.

I'm sure we're all glad to see that things are working much better today.

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 6:59 pm
by weedacres
I guess I spoke too soon before regarding 171.64.65.71, I have 2 clients down waiting for work.

Code: Select all

[18:35:25] + Attempting to send results [February 22 18:35:25 UTC]
[18:35:25] - Reading file work/wuresults_03.dat from core
[18:35:25]   (Read 132333 bytes from disk)
[18:35:25] Connecting to http://171.64.65.71:8080/
[18:35:30] Posted data.
[18:35:30] Initial: 0000; - Uploaded at ~26 kB/s
[18:35:30] - Averaged speed for that direction ~36 kB/s
[18:35:30] + Results successfully sent
[18:35:30] Thank you for your contribution to Folding@Home.
[18:35:30] + Number of Units Completed: 4360

[18:35:34] Trying to send all finished work units
[18:35:34] + No unsent completed units remaining.
[18:35:34] - Preparing to get new work unit...
[18:35:34] + Attempting to get work packet
[18:35:34] - Will indicate memory of 3070 MB
[18:35:34] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 15, Stepping: 11
[18:35:34] - Connecting to assignment server
[18:35:34] Connecting to http://assign-GPU.stanford.edu:8080/
[18:35:35] Posted data.
[18:35:35] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:35:35] + News From Folding@Home: Welcome to Folding@Home
[18:35:35] Loaded queue successfully.
[18:35:35] Connecting to http://171.64.65.71:8080/
[18:35:35] - Couldn't send HTTP request to server
[18:35:35] + Could not connect to Work Server
[18:35:35] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[18:35:53] + Attempting to get work packet
[18:35:53] - Will indicate memory of 3070 MB
[18:35:53] - Connecting to assignment server
[18:35:53] Connecting to http://assign-GPU.stanford.edu:8080/
[18:35:54] Posted data.
[18:35:54] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:35:54] + News From Folding@Home: Welcome to Folding@Home
[18:35:54] Loaded queue successfully.
[18:35:54] Connecting to http://171.64.65.71:8080/
[18:35:54] - Couldn't send HTTP request to server
[18:35:54] + Could not connect to Work Server
[18:35:54] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[18:36:16] + Attempting to get work packet
[18:36:16] - Will indicate memory of 3070 MB
[18:36:16] - Connecting to assignment server
[18:36:16] Connecting to http://assign-GPU.stanford.edu:8080/
[18:36:17] Posted data.
[18:36:17] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:36:17] + News From Folding@Home: Welcome to Folding@Home
[18:36:17] Loaded queue successfully.
[18:36:17] Connecting to http://171.64.65.71:8080/
[18:36:17] - Couldn't send HTTP request to server
[18:36:17] + Could not connect to Work Server
[18:36:17] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[18:36:50] + Attempting to get work packet
[18:36:50] - Will indicate memory of 3070 MB
[18:36:50] - Connecting to assignment server
[18:36:50] Connecting to http://assign-GPU.stanford.edu:8080/
[18:36:50] Posted data.
[18:36:50] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:36:50] + News From Folding@Home: Welcome to Folding@Home
[18:36:50] Loaded queue successfully.
[18:36:50] Connecting to http://171.64.65.71:8080/
[18:36:51] - Couldn't send HTTP request to server
[18:36:51] + Could not connect to Work Server
[18:36:51] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[18:37:45] + Attempting to get work packet
[18:37:45] - Will indicate memory of 3070 MB
[18:37:45] - Connecting to assignment server
[18:37:45] Connecting to http://assign-GPU.stanford.edu:8080/
[18:37:46] Posted data.
[18:37:46] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:37:46] + News From Folding@Home: Welcome to Folding@Home
[18:37:46] Loaded queue successfully.
[18:37:46] Connecting to http://171.64.65.71:8080/
[18:37:46] - Couldn't send HTTP request to server
[18:37:46] + Could not connect to Work Server
[18:37:46] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[18:39:20] + Attempting to get work packet
[18:39:20] - Will indicate memory of 3070 MB
[18:39:20] - Connecting to assignment server
[18:39:20] Connecting to http://assign-GPU.stanford.edu:8080/
[18:39:20] Posted data.
[18:39:20] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:39:20] + News From Folding@Home: Welcome to Folding@Home
[18:39:20] Loaded queue successfully.
[18:39:20] Connecting to http://171.64.65.71:8080/
[18:39:20] - Couldn't send HTTP request to server
[18:39:20] + Could not connect to Work Server
[18:39:20] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[18:42:10] + Attempting to get work packet
[18:42:10] - Will indicate memory of 3070 MB
[18:42:10] - Connecting to assignment server
[18:42:10] Connecting to http://assign-GPU.stanford.edu:8080/
[18:42:10] Posted data.
[18:42:10] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:42:10] + News From Folding@Home: Welcome to Folding@Home
[18:42:10] Loaded queue successfully.
[18:42:10] Connecting to http://171.64.65.71:8080/
[18:42:11] - Couldn't send HTTP request to server
[18:42:11] + Could not connect to Work Server
[18:42:11] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 7:12 pm
by Leonardo
things are working much better today
...but an unexpected storm front....

As of 1005 hrs Alaskan Time/1105 Pacific Time, 11 GPU clients without work. (Yes, I imagine the server guys are hard at work on this. I'm supplying information for whatever purpose it may serve.)

Last completed work units on the subject clients were accepted by servers 171.64.65.20, 171.67.108.21, and 171.64.65.71 (yeah, I know, I thought ~71 at was only an assignment server). Failed attempts at downloading new work units have all been with assignment server 171.64.65.71. Since the failed assignments began a couple hours ago on 71, no GPU clients of mine have been assigned to any assignment servers other than ~71.

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 7:19 pm
by noorman
weedacres wrote:I guess I spoke too soon before regarding 171.64.65.71, I have 2 clients down waiting for work.

Code: Select all

[18:35:25] + Attempting to send results [February 22 18:35:25 UTC]
[18:35:25] - Reading file work/wuresults_03.dat from core
[18:35:25]   (Read 132333 bytes from disk)
[18:35:25] Connecting to http://171.64.65.71:8080/
[18:35:30] Posted data.
[18:35:30] Initial: 0000; - Uploaded at ~26 kB/s
[18:35:30] - Averaged speed for that direction ~36 kB/s
[18:35:30] + Results successfully sent
[18:35:30] Thank you for your contribution to Folding@Home.
[18:35:30] + Number of Units Completed: 4360

[18:35:34] Trying to send all finished work units
[18:35:34] + No unsent completed units remaining.
[18:35:34] - Preparing to get new work unit...
[18:35:34] + Attempting to get work packet
[18:35:34] - Will indicate memory of 3070 MB
[18:35:34] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 15, Stepping: 11
[18:35:34] - Connecting to assignment server
[18:35:34] Connecting to http://assign-GPU.stanford.edu:8080/
[18:35:35] Posted data.
[18:35:35] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:35:35] + News From Folding@Home: Welcome to Folding@Home
[18:35:35] Loaded queue successfully.
[18:35:35] Connecting to http://171.64.65.71:8080/
[18:35:35] - Couldn't send HTTP request to server
[18:35:35] + Could not connect to Work Server
[18:35:35] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[18:35:53] + Attempting to get work packet
[18:35:53] - Will indicate memory of 3070 MB
[18:35:53] - Connecting to assignment server
[18:35:53] Connecting to http://assign-GPU.stanford.edu:8080/
[18:35:54] Posted data.
[18:35:54] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:35:54] + News From Folding@Home: Welcome to Folding@Home
[18:35:54] Loaded queue successfully.
[18:35:54] Connecting to http://171.64.65.71:8080/
[18:35:54] - Couldn't send HTTP request to server
[18:35:54] + Could not connect to Work Server
[18:35:54] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[18:36:16] + Attempting to get work packet
[18:36:16] - Will indicate memory of 3070 MB
[18:36:16] - Connecting to assignment server
[18:36:16] Connecting to http://assign-GPU.stanford.edu:8080/
[18:36:17] Posted data.
[18:36:17] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:36:17] + News From Folding@Home: Welcome to Folding@Home
[18:36:17] Loaded queue successfully.
[18:36:17] Connecting to http://171.64.65.71:8080/
[18:36:17] - Couldn't send HTTP request to server
[18:36:17] + Could not connect to Work Server
[18:36:17] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[18:36:50] + Attempting to get work packet
[18:36:50] - Will indicate memory of 3070 MB
[18:36:50] - Connecting to assignment server
[18:36:50] Connecting to http://assign-GPU.stanford.edu:8080/
[18:36:50] Posted data.
[18:36:50] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:36:50] + News From Folding@Home: Welcome to Folding@Home
[18:36:50] Loaded queue successfully.
[18:36:50] Connecting to http://171.64.65.71:8080/
[18:36:51] - Couldn't send HTTP request to server
[18:36:51] + Could not connect to Work Server
[18:36:51] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[18:37:45] + Attempting to get work packet
[18:37:45] - Will indicate memory of 3070 MB
[18:37:45] - Connecting to assignment server
[18:37:45] Connecting to http://assign-GPU.stanford.edu:8080/
[18:37:46] Posted data.
[18:37:46] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:37:46] + News From Folding@Home: Welcome to Folding@Home
[18:37:46] Loaded queue successfully.
[18:37:46] Connecting to http://171.64.65.71:8080/
[18:37:46] - Couldn't send HTTP request to server
[18:37:46] + Could not connect to Work Server
[18:37:46] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[18:39:20] + Attempting to get work packet
[18:39:20] - Will indicate memory of 3070 MB
[18:39:20] - Connecting to assignment server
[18:39:20] Connecting to http://assign-GPU.stanford.edu:8080/
[18:39:20] Posted data.
[18:39:20] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:39:20] + News From Folding@Home: Welcome to Folding@Home
[18:39:20] Loaded queue successfully.
[18:39:20] Connecting to http://171.64.65.71:8080/
[18:39:20] - Couldn't send HTTP request to server
[18:39:20] + Could not connect to Work Server
[18:39:20] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[18:42:10] + Attempting to get work packet
[18:42:10] - Will indicate memory of 3070 MB
[18:42:10] - Connecting to assignment server
[18:42:10] Connecting to http://assign-GPU.stanford.edu:8080/
[18:42:10] Posted data.
[18:42:10] Initial: 40AB; - Successful: assigned to (171.64.65.71).
[18:42:10] + News From Folding@Home: Welcome to Folding@Home
[18:42:10] Loaded queue successfully.
[18:42:10] Connecting to http://171.64.65.71:8080/
[18:42:11] - Couldn't send HTTP request to server
[18:42:11] + Could not connect to Work Server
[18:42:11] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
.


Very odd; all my latest Work comes from 171.64.65.71:8080 without fail (1st attempt) :eo


.

Re: GPU server status 171.67.108.21, 171.64.65.71,171.67.108.26

Posted: Mon Feb 22, 2010 7:22 pm
by tobor
No work either...

Code: Select all

###############################################################################
###############################################################################

Launch directory: C:\Documents and Settings\steve\Application Data\Folding@home-gpu
Arguments: -gpu 0 

[18:54:12] - Ask before connecting: No
[18:54:12] - User name: stv911 (Team 4)
[18:54:12] - User ID: BE4069840F022A4
[18:54:12] - Machine ID: 2
[18:54:12] 
[18:54:12] Loaded queue successfully.
[18:54:12] Initialization complete
[18:54:12] 
[18:54:12] + Processing work unit
[18:54:12] Core required: FahCore_14.exe
[18:54:12] Core found.
[18:54:12] Working on queue slot 02 [February 22 18:54:12 UTC]
[18:54:12] + Working ...
[18:54:12] 
[18:54:12] *------------------------------*
[18:54:12] Folding@Home GPU Core - Beta
[18:54:12] Version 1.26 (Wed Oct 14 13:09:26 PDT 2009)
[18:54:12] 
[18:54:12] Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
[18:54:12] Build host: vspm46
[18:54:12] Board Type: Nvidia
[18:54:12] Core      : 
[18:54:12] Preparing to commence simulation
[18:54:12] - Looking at optimizations...
[18:54:12] - Files status OK
[18:54:12] - Expanded 70198 -> 360060 (decompressed 512.9 percent)
[18:54:12] Called DecompressByteArray: compressed_data_size=70198 data_size=360060, decompressed_data_size=360060 diff=0
[18:54:12] - Digital signature verified
[18:54:12] 
[18:54:12] Project: 5910 (Run 5, Clone 176, Gen 15)
[18:54:12] 
[18:54:12] Assembly optimizations on if available.
[18:54:12] Entering M.D.
[18:54:18] Will resume from checkpoint file
[18:54:18] Tpr hash work/wudata_02.tpr:  2838954921 590447164 3600575590 2789920116 2474626801
[18:54:18] Working on Protein
[18:54:19] Client config found, loading data.
[18:54:19] Resuming from checkpoint
[18:54:19] fcCheckPointResume: retrieved and current tpr file hash:
[18:54:19]    0   2838954921   2838954921
[18:54:19]    1    590447164    590447164
[18:54:19]    2   3600575590   3600575590
[18:54:19]    3   2789920116   2789920116
[18:54:19]    4   2474626801   2474626801
[18:54:19] Verified work/wudata_02.log
[18:54:19] Verified work/wudata_02.edr
[18:54:19] Verified work/wudata_02.xtc
[18:54:19] Completed 99%
[18:54:19] Starting GUI Server
[18:54:56] Completed 100%
[18:54:56] Successful run
[18:54:56] DynamicWrapper: Finished Work Unit: sleep=10000
[18:55:06] Reserved 11336 bytes for xtc file; Cosm status=0
[18:55:06] Allocated 11336 bytes for xtc file
[18:55:06] - Reading up to 11336 from "work/wudata_02.xtc": Read 11336
[18:55:06] Read 11336 bytes from xtc file; available packet space=786419128
[18:55:06] xtc file hash check passed.
[18:55:06] Reserved 23472 23472 786419128 bytes for arc file=<work/wudata_02.trr> Cosm status=0
[18:55:06] Allocated 23472 bytes for arc file
[18:55:06] - Reading up to 23472 from "work/wudata_02.trr": Read 23472
[18:55:06] Read 23472 bytes from arc file; available packet space=786395656
[18:55:06] trr file hash check passed.
[18:55:06] Allocated 560 bytes for edr file
[18:55:06] Read bedfile
[18:55:06] edr file hash check passed.
[18:55:06] Allocated 81209 bytes for logfile
[18:55:06] Read logfile
[18:55:06] GuardedRun: success in DynamicWrapper
[18:55:06] GuardedRun: done
[18:55:06] Run: GuardedRun completed.
[18:55:07] - Writing 117089 bytes of core data to disk...
[18:55:07] Done: 116577 -> 43881 (compressed to 37.6 percent)
[18:55:07]   ... Done.
[18:55:07] - Shutting down core 
[18:55:07] 
[18:55:07] Folding@home Core Shutdown: FINISHED_UNIT
[18:55:10] CoreStatus = 64 (100)
[18:55:10] Sending work to server
[18:55:10] Project: 5910 (Run 5, Clone 176, Gen 15)


[18:55:10] + Attempting to send results [February 22 18:55:10 UTC]
[18:55:11] + Results successfully sent
[18:55:11] Thank you for your contribution to Folding@Home.
[18:55:11] + Number of Units Completed: 262

[18:55:15] - Preparing to get new work unit...
[18:55:15] + Attempting to get work packet
[18:55:15] - Connecting to assignment server
[18:55:15] - Successful: assigned to (171.64.65.71).
[18:55:15] + News From Folding@Home: Welcome to Folding@Home
[18:55:16] Loaded queue successfully.
[18:55:16] - Couldn't send HTTP request to server
[18:55:16] + Could not connect to Work Server
[18:55:16] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[18:55:34] + Attempting to get work packet
[18:55:34] - Connecting to assignment server
[18:55:35] - Successful: assigned to (171.64.65.71).
[18:55:35] + News From Folding@Home: Welcome to Folding@Home
[18:55:35] Loaded queue successfully.
[18:55:35] - Couldn't send HTTP request to server
[18:55:35] + Could not connect to Work Server
[18:55:35] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[18:55:48] + Attempting to get work packet
[18:55:48] - Connecting to assignment server
[18:55:49] - Successful: assigned to (171.64.65.71).
[18:55:49] + News From Folding@Home: Welcome to Folding@Home
[18:55:49] Loaded queue successfully.
[18:55:49] - Couldn't send HTTP request to server
[18:55:49] + Could not connect to Work Server
[18:55:49] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[18:56:14] + Attempting to get work packet
[18:56:14] - Connecting to assignment server
[18:56:14] - Successful: assigned to (171.64.65.71).
[18:56:14] + News From Folding@Home: Welcome to Folding@Home
[18:56:14] Loaded queue successfully.
[18:56:15] - Couldn't send HTTP request to server
[18:56:15] + Could not connect to Work Server
[18:56:15] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[18:57:07] + Attempting to get work packet
[18:57:07] - Connecting to assignment server
[18:57:07] - Successful: assigned to (171.64.65.71).
[18:57:07] + News From Folding@Home: Welcome to Folding@Home
[18:57:07] Loaded queue successfully.
[18:57:07] - Couldn't send HTTP request to server
[18:57:07] + Could not connect to Work Server
[18:57:07] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.

Folding@Home Client Shutdown.


--- Opening Log file [February 22 19:07:35 UTC] 


# Windows GPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Documents and Settings\steve\Application Data\Folding@home-gpu
Arguments: -gpu 0 

[19:07:35] - Ask before connecting: No
[19:07:35] - User name: stv911 (Team 4)
[19:07:35] - User ID: BE4069840F022A4
[19:07:35] - Machine ID: 2
[19:07:35] 
[19:07:35] Loaded queue successfully.
[19:07:35] Initialization complete
[19:07:35] - Preparing to get new work unit...
[19:07:35] + Attempting to get work packet
[19:07:35] - Connecting to assignment server
[19:07:36] - Successful: assigned to (171.64.65.71).
[19:07:36] + News From Folding@Home: Welcome to Folding@Home
[19:07:36] Loaded queue successfully.
[19:07:37] - Couldn't send HTTP request to server
[19:07:37] + Could not connect to Work Server
[19:07:37] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[19:07:47] + Attempting to get work packet
[19:07:47] - Connecting to assignment server
[19:07:47] - Successful: assigned to (171.64.65.71).
[19:07:47] + News From Folding@Home: Welcome to Folding@Home
[19:07:47] Loaded queue successfully.
[19:07:48] - Couldn't send HTTP request to server
[19:07:48] + Could not connect to Work Server
[19:07:48] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[19:08:10] + Attempting to get work packet
[19:08:10] - Connecting to assignment server
[19:08:10] - Successful: assigned to (171.64.65.71).
[19:08:10] + News From Folding@Home: Welcome to Folding@Home
[19:08:10] Loaded queue successfully.
[19:08:11] - Couldn't send HTTP request to server
[19:08:11] + Could not connect to Work Server
[19:08:11] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[19:08:44] + Attempting to get work packet
[19:08:44] - Connecting to assignment server
[19:08:45] - Successful: assigned to (171.64.65.71).
[19:08:45] + News From Folding@Home: Welcome to Folding@Home
[19:08:45] Loaded queue successfully.
[19:08:45] - Couldn't send HTTP request to server
[19:08:45] + Could not connect to Work Server
[19:08:45] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[19:09:38] + Attempting to get work packet
[19:09:38] - Connecting to assignment server
[19:09:38] - Successful: assigned to (171.64.65.71).
[19:09:38] + News From Folding@Home: Welcome to Folding@Home
[19:09:38] Loaded queue successfully.
[19:09:39] - Couldn't send HTTP request to server
[19:09:39] + Could not connect to Work Server
[19:09:39] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[19:11:06] + Attempting to get work packet
[19:11:06] - Connecting to assignment server
[19:11:07] - Successful: assigned to (171.64.65.71).
[19:11:07] + News From Folding@Home: Welcome to Folding@Home
[19:11:07] Loaded queue successfully.
[19:11:07] - Couldn't send HTTP request to server
[19:11:07] + Could not connect to Work Server
[19:11:07] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.

Folding@Home Client Shutdown.


--- Opening Log file [February 22 19:13:13 UTC] 


# Windows GPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Documents and Settings\steve\Application Data\Folding@home-gpu
Arguments: -gpu 0 

[19:13:13] - Ask before connecting: No
[19:13:13] - User name: stv911 (Team 4)
[19:13:13] - User ID: BE4069840F022A4
[19:13:13] - Machine ID: 2
[19:13:13] 
[19:13:13] Loaded queue successfully.
[19:13:13] Initialization complete
[19:13:13] - Preparing to get new work unit...
[19:13:13] + Attempting to get work packet
[19:13:13] - Connecting to assignment server
[19:13:14] - Successful: assigned to (171.64.65.71).
[19:13:14] + News From Folding@Home: Welcome to Folding@Home
[19:13:14] Loaded queue successfully.
[19:13:14] - Couldn't send HTTP request to server
[19:13:14] + Could not connect to Work Server
[19:13:14] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[19:13:29] + Attempting to get work packet
[19:13:29] - Connecting to assignment server
[19:13:30] - Successful: assigned to (171.64.65.71).
[19:13:30] + News From Folding@Home: Welcome to Folding@Home
[19:13:30] Loaded queue successfully.
[19:13:30] - Couldn't send HTTP request to server
[19:13:30] + Could not connect to Work Server
[19:13:30] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[19:13:41] + Attempting to get work packet
[19:13:41] - Connecting to assignment server
[19:13:42] - Successful: assigned to (171.64.65.71).
[19:13:42] + News From Folding@Home: Welcome to Folding@Home
[19:13:42] Loaded queue successfully.
[19:13:42] - Couldn't send HTTP request to server
[19:13:42] + Could not connect to Work Server
[19:13:42] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[19:14:05] + Attempting to get work packet
[19:14:05] - Connecting to assignment server
[19:14:06] - Successful: assigned to (171.64.65.71).
[19:14:06] + News From Folding@Home: Welcome to Folding@Home
[19:14:06] Loaded queue successfully.
[19:14:06] - Couldn't send HTTP request to server
[19:14:06] + Could not connect to Work Server
[19:14:06] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[19:15:00] + Attempting to get work packet
[19:15:00] - Connecting to assignment server
[19:15:00] - Successful: assigned to (171.64.65.71).
[19:15:00] + News From Folding@Home: Welcome to Folding@Home
[19:15:00] Loaded queue successfully.
[19:15:01] - Couldn't send HTTP request to server
[19:15:01] + Could not connect to Work Server
[19:15:01] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.