Attempting to send results, can't get work

[lambdapro]

I have a working system that had been running just fine since I turned it on for the winter a week ago when it got cooler. But a couple of hours ago, it gave me this:

[01:59:44] - Ask before connecting: No
[01:59:44] - User name: David_GX270 (Team 177289)
[01:59:44] - User ID: 3D5C07A935930E01
[01:59:44] - Machine ID: 2
[01:59:44]
[01:59:44] Loaded queue successfully.
[01:59:45] Initialization complete
[01:59:45] - Preparing to get new work unit...
[01:59:45] + Attempting to get work packet
[01:59:45] Project: 5734 (Run 4, Clone 592, Gen 26)


[01:59:45] + Attempting to send results [December 2 01:59:45 UTC]
[01:59:45] - Connecting to assignment server
[01:59:45] + No appropriate work server was available; will try again in a bit.
[01:59:45] + Couldn't get work instructions.
[01:59:45] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[01:59:46] - Couldn't send HTTP request to server
[01:59:46] + Could not connect to Work Server (results)
[01:59:46] (171.64.65.102:8080)
[01:59:46] + Retrying using alternative port
[01:59:47] - Couldn't send HTTP request to server
[01:59:47] + Could not connect to Work Server (results)
[01:59:47] (171.64.65.102:80)
[01:59:47] - Error: Could not transmit unit 08 (completed December 1) to work server.


[01:59:47] + Attempting to send results [December 2 01:59:47 UTC]
[01:59:47] - Couldn't send HTTP request to server
[01:59:47] (Got status 503)
[01:59:47] + Could not connect to Work Server (results)
[01:59:47] (171.67.108.17:8080)
[01:59:47] + Retrying using alternative port
[01:59:47] - Couldn't send HTTP request to server
[01:59:47] (Got status 503)
[01:59:47] + Could not connect to Work Server (results)
[01:59:47] (171.67.108.17:80)
[01:59:47] Could not transmit unit 08 to Collection server; keeping in queue.

Let me know when I should fire it back up.

Shutting down systems here to save electricity.

David

[bruce]

Server 171.64.65.102 is rejecting connections and the only other server with ATI WUs is 171.64.65.103 which is low on WUs right now. I've reported it to the server's owner.

[GreyWhiskers]

a) I've also been locked out of sending my last WU and retrieving my next. See latest snippet, and when I started to send the latest unit at 4:19.

Code: Select all

[04:19:20] Folding@home Core Shutdown: FINISHED_UNIT
[04:19:23] CoreStatus = 64 (100)
[04:19:23] Unit 5 finished with 86 percent of time to deadline remaining.
[04:19:23] Updated performance fraction: 0.856706
[04:19:23] Sending work to server
[04:19:23] Project: 5732 (Run 4, Clone 620, Gen 30)
[04:19:23] - Read packet limit of 540015616... Set to 524286976.


[04:19:23] + Attempting to send results [December 2 04:19:23 UTC]
[04:19:23] - Reading file work/wuresults_05.dat from core
[04:19:23]   (Read 263877 bytes from disk)
[04:19:23] Gpu type=1 species=3.
[04:19:23] Connecting to http://171.64.65.102:8080/
[04:19:24] - Couldn't send HTTP request to server
[04:19:24] + Could not connect to Work Server (results)
[04:19:24]     (171.64.65.102:8080)
[04:19:24] + Retrying using alternative port
[04:19:24] Connecting to http://171.64.65.102:80/
[04:19:25] - Couldn't send HTTP request to server
[04:19:25] + Could not connect to Work Server (results)
[04:19:25]     (171.64.65.102:80)
[04:19:25] - Error: Could not transmit unit 05 (completed December 2) to work server.
[04:19:25] - 1 failed uploads of this unit.
[04:19:25]   Keeping unit 05 in queue.

.......

[05:25:45] + Attempting to send results [December 2 05:25:45 UTC]
[05:25:45] - Reading file work/wuresults_05.dat from core
[05:25:45]   (Read 263877 bytes from disk)
[05:25:45] Gpu type=1 species=3.
[05:25:45] Connecting to http://171.67.108.17:8080/
[05:25:45] Posted data.
[05:25:45] Initial: 5448; + Could not connect to Work Server (results)
[05:25:45]     (171.67.108.17:8080)
[05:25:45] + Retrying using alternative port
[05:25:45] Connecting to http://171.67.108.17:80/
[05:25:45] Posted data.
[05:25:45] Initial: 5448; + Could not connect to Work Server (results)
[05:25:45]     (171.67.108.17:80)
[05:25:45]   Could not transmit unit 05 to Collection server; keeping in queue.
[05:25:45] + Sent 0 of 1 completed units to the server
[05:25:45] - Autosend completed
[05:46:15] + Attempting to get work packet
[05:46:15] Passkey found
[05:46:15] - Will indicate memory of 2047 MB
[05:46:15] Gpu type=1 species=3.
[05:46:15] - Connecting to assignment server
[05:46:15] Connecting to http://assign-GPU.stanford.edu:8080/
[05:46:15] Posted data.
[05:46:15] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[05:46:15] + Couldn't get work instructions.
[05:46:15] - Attempt #11  to get work failed, and no other work to do.
Waiting before retry.

b) What happened to the 384 point WUs that this server used to send out? Since 20 Nov, I've gotten nothing but an unbroken string of twenty six 511 point WUs for my ATI 4670.

Thanks.

Al

[bruce]

What happened to the 384 point WUs that this server used to send out? Since 20 Nov, I've gotten nothing but an unbroken string of twenty six 511 point WUs for my ATI 4670.

There's no answer to a question like that. Projects come and go without notice.

When a new project is added, it's because somebody on the science side put together a project to study a particular protein or a particular interaction. They don't pick projects with a particular number of points; the number of points depends on the complexity of the WU. When enough data has been collected on a particular project, new assignments are no longer issued and the results are analyzed off-line. That analysis may lead to a scientific paper or it may lead to some new questions being asked about areas that were not covered in the original analysis -- or if something totally unexpected is encountered, a whole new study may be launched.

[bruce]

Server 171.64.65.102 is rejecting connections and the only other server with ATI WUs is 171.64.65.103 which is low on WUs right now. I've reported it to the server's owner.

This seems to have been fixed. Hopefully you'll be returning WUs and getting new assignments now.

[lambdapro]

That got it going again. TKS
David