Folding:Server does not have record of this unit. Will try again later, error?

Distributed Computing Projects Folding @ Home
1

got Server does not have record of this unit. Will try again later in the log, any ideas?


[17:45:18] + Attempting to send results
[17:46:11] - Server does not have record of this unit. Will try again later.
[17:46:11]   Could not transmit unit 07 to Collection server; keeping in queue.
[17:46:11] - Preparing to get new work unit...
[17:46:11] + Attempting to get work packet
[17:46:11] - Connecting to assignment server
[17:46:12] - Successful: assigned to (171.64.122.141).
[17:46:12] + News From Folding@Home: Welcome to Folding@Home
[17:46:12] Loaded queue successfully.


[17:46:16] + Attempting to send results
[17:46:17] - Couldn't send HTTP request to server
[17:46:17] + Could not connect to Work Server (results)
[17:46:17]     (171.64.122.136:8080)
[17:46:17] - Error: Could not transmit unit 07 (completed June 17) to work server.


[17:46:17] + Attempting to send results
[17:47:11] - Server does not have record of this unit. Will try again later.
[17:47:11]   Could not transmit unit 07 to Collection server; keeping in queue.
[17:47:11] + Closed connections

Curly

2

saw this the other day on the Folding forums, as such I’ve not seen a reply to what is happening. :frowning: To give us a clue can you read back and find the project number.

DT.

3 

Project: 2098 (Run 75, Clone 39, Gen 2)
[15:39:01] 
[15:39:01] Assembly optimizations on if available.
[15:39:01] Entering M.D.
[15:39:07] Protein: p2098_abeta_agbnp

Curly

4

Just checked some of my machines - I had at least one stuck with the same “no record of the unit” error on the same server, but it finally uploaded to the collection server:

[16:24:37] - Starting from initial work packet
[16:24:37]
[16:24:37] Project: 2095 (Run 203, Clone 56, Gen 5)
…
[19:13:09] Writing final coordinates.
[19:13:09] Past main M.D. loop
[19:14:09]
[19:14:09] Finished Work Unit:
[19:14:09] - Reading up to 6456 from “work/wudata_03.arc”: Read 6456
[19:14:09] - Reading up to 270032 from “work/wudata_03.xtc”: Read 270032
[19:14:09] goefile size: 0
[19:14:09] logfile size: 506240
[19:14:09] Leaving Run
[19:14:13] - Writing 948496 bytes of core data to disk…
[19:14:13] … Done.
[19:14:14] - Shutting down core
[19:14:14]
[19:14:14] Folding@home Core Shutdown: FINISHED_UNIT
[19:14:14] CoreStatus = 64 (100)
[19:14:14] Sending work to server
[19:14:14] + Attempting to send results
[19:14:14] - Couldn’t send HTTP request to server
[19:14:14] + Could not connect to Work Server (results)
[19:14:14] (171.64.122.136:8080)
[19:14:14] - Error: Could not transmit unit 03 (completed June 17) to work server.
[19:14:14] Keeping unit 03 in queue.
[19:14:14] + Attempting to send results
[19:14:14] - Couldn’t send HTTP request to server
[19:14:14] + Could not connect to Work Server (results)
[19:14:14] (171.64.122.136:8080)
[19:14:14] - Error: Could not transmit unit 03 (completed June 17) to work server.
[19:14:14] + Attempting to send results
[19:14:46] - Server does not have record of this unit. Will try again later.
[19:14:46] Could not transmit unit 03 to Collection server; keeping in queue.

Then…

[20:13:43] + Attempting to send results
[20:13:43] - Couldn’t send HTTP request to server
[20:13:43] + Could not connect to Work Server (results)
[20:13:43] (171.64.122.136:8080)
[20:13:43] - Error: Could not transmit unit 03 (completed June 17) to work server.
[20:13:43] + Attempting to send results
[20:14:16] + Results successfully sent
[20:14:16] Thank you for your contribution to Folding@Home.
[20:14:16] + Number of Units Completed: 13
[20:14:16] Successfully sent unit 03 to Collection server.

Seems odd that the assignment server should not have a record of the unit:confused:

5

I have seen this on F-C.org as well. I’ll try to get someone to take a look.

@Curly: Server .141 has an extremly high cpu load, so you are being bumped to the default collection server (.136) which is rejecting connections.

@Nightlord: Your also trying to return work to .136, and its rejecting connections.

My advice to both of you is to wait and see. It should clear up eventually.

Server Status

171.64.122.136 - Test Connection

6

finally got it sent after re-starting the client a few times


[22:10:18] + Attempting to send results
[22:10:18] 
[22:10:18] *------------------------------*
[22:10:18] Folding@Home Gromacs Core
[22:10:18] Version 1.86 (August 28, 2005)
[22:10:18] 
[22:10:18] Preparing to commence simulation
[22:10:18] - Assembly optimizations manually forced on.
[22:10:18] - Not checking prior termination.
[22:10:18] - Expanded 78980 -> 419621 (decompressed 531.3 percent)
[22:10:18] 
[22:10:18] Project: 2107 (Run 36, Clone 48, Gen 10)
[22:10:18] 
[22:10:18] Assembly optimizations on if available.
[22:10:18] Entering M.D.
[22:10:19] - Couldn't send HTTP request to server
[22:10:19] + Could not connect to Work Server (results)
[22:10:19]     (171.64.122.136:8080)
[22:10:19] - Error: Could not transmit unit 07 (completed June 17) to work server.


[22:10:19] + Attempting to send results
[22:10:39] (Starting from checkpoint)
[22:10:39] Protein: p2107_lambda_5way_melt_4_10011
[22:10:39] 
[22:10:39] Writing local files
[22:10:39] Using table 1
[22:10:39] Completed 1000000 out of 20000000 steps  (5)
[22:10:39] Extra SSE boost OK.
[22:11:13] + Results successfully sent
[22:11:13] Thank you for your contribution to Folding@Home.
[22:11:13] + Number of Units Completed: 116

[22:11:13]   Successfully sent unit 07 to Collection server.

Curly

7

Must have just squeeked it in because the CPU load is even higher!

8

Prof. Vijay Pande at Stanford says he is going to look into this issue with .136 and the “Server does not have a record of this unit” message.

9

Get the same error again with sever 136, took a look at the thread over at the folding forums and no real solution except to keep trying to upload till it does go through… somethings not right there end.

Curly

10

I also got it on my computer, but it eventually got throught. If it doesnt send within a day or two report it to Prof.Pande

11

The problem always clears itself up when you let it try over and over again. Its caused by the server not reporting the units existance to the collection server before the unit is uploaded.

12

yeah unit eventualy went up today, so all ends well, but always seems to be server 136.

Curly

13

I would presume that’s because you are almost exclusively receiving work from 136 - it is the advmethods server after all :wink:

14

Thanks for the info Mulda, I didn’t know that was the advmethods server.

Curly

15

A way you can tell what each server does is look at this page:

http://fah-web.stanford.edu/serverstat.html

If you scroll over, under the heading “PROGRAM” There are several letters:

F - Folding@home (General work units)
A - Advanced Methods
B - Beta Units
I - Internal Testing
G - Genome@home