Getting "Exception: Have already seen this work unit" errors

[[Ars] For Caitlin]

These are starting to occur with frequency from different work servers. Not sure if this indicates a problem on my end with something corrupted or on the server end (unlikely).

Code: Select all

22:35:58:WU00:FS00:Connecting to assign1.foldingathome.org:80
22:35:59:WU00:FS00:Assigned to work server 128.174.73.74
22:35:59:WU00:FS00:Requesting new work unit for slot 00: gpu:9:0 Navi 21 [Radeon RX 6900 XT] from 128.174.73.74
22:35:59:WU00:FS00:Connecting to 128.174.73.74:8080
22:36:01:ERROR:WU00:FS00:Exception: Have already seen this work unit 0x00000000000000000000000001000000 aborting download
22:36:34:WU01:FS00:0x22:Completed 500000 out of 500000 steps (100%)
22:36:34:WU01:FS00:0x22:Average performance: 23.6712 ns/day
22:36:36:WU01:FS00:0x22:Checkpoint completed at step 500000
22:36:45:WU01:FS00:0x22:Saving result file ..\logfile_01.txt
22:36:45:WU01:FS00:0x22:Saving result file checkpointIntegrator.xml
22:36:45:WU01:FS00:0x22:Saving result file checkpointState.xml
22:36:50:WU01:FS00:0x22:Saving result file positions.xtc
22:36:50:WU01:FS00:0x22:Saving result file science.log
22:36:50:WU01:FS00:0x22:Saving result file xtcAtoms.csv.bz2
22:36:50:WU01:FS00:0x22:Folding@home Core Shutdown: FINISHED_UNIT
22:36:51:WU01:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
22:36:51:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:12424 run:2 clone:433 gen:393 core:0x22 unit:0x000001b1000001890000308800000002
22:36:51:WU01:FS00:Uploading 35.36MiB to 129.32.209.200
22:36:51:WU01:FS00:Connecting to 129.32.209.200:8080
22:36:58:WU01:FS00:Upload 10.61%
22:36:59:WU00:FS00:Connecting to assign1.foldingathome.org:80
22:36:59:WU00:FS00:Assigned to work server 66.170.111.50
22:36:59:WU00:FS00:Requesting new work unit for slot 00: gpu:9:0 Navi 21 [Radeon RX 6900 XT] from 66.170.111.50
22:36:59:WU00:FS00:Connecting to 66.170.111.50:8080
22:37:05:WU01:FS00:Upload 10.78%
22:37:11:ERROR:WU00:FS00:Exception: Have already seen this work unit 0x00000000000000000000000001000000 aborting download
22:37:13:WU01:FS00:Upload 10.96%
22:37:21:WU01:FS00:Upload 12.73%
22:37:29:WU01:FS00:Upload 12.90%
22:37:37:WU01:FS00:Upload 13.08%
22:37:41:WU01:FS00:Upload complete
22:37:41:WU01:FS00:Server responded WORK_ACK (400)
22:37:41:WU01:FS00:Final credit estimate, 273102.00 points
22:37:42:WU01:FS00:Cleaning up
22:38:36:WU00:FS00:Connecting to assign1.foldingathome.org:80
22:38:36:WU00:FS00:Assigned to work server 128.174.73.74
22:38:37:WU00:FS00:Requesting new work unit for slot 00: gpu:9:0 Navi 21 [Radeon RX 6900 XT] from 128.174.73.74
22:38:37:WU00:FS00:Connecting to 128.174.73.74:8080
22:38:37:ERROR:WU00:FS00:Exception: Server did not assign work unit
22:41:13:WU00:FS00:Connecting to assign1.foldingathome.org:80
22:41:14:WU00:FS00:Assigned to work server 128.174.73.74
22:41:14:WU00:FS00:Requesting new work unit for slot 00: gpu:9:0 Navi 21 [Radeon RX 6900 XT] from 128.174.73.74
22:41:14:WU00:FS00:Connecting to 128.174.73.74:8080
22:41:26:ERROR:WU00:FS00:Exception: Have already seen this work unit 0x00000000000000000000000001000000 aborting download

[Joe_H]

Best I can say is check both your current log file and the older stored log files to see if you actually had processed a particular WU before. If not, then it is possible particular project(s) or server(s) could have an incorrect setting or bug. Normally the servers will only send a WU out to a particular system once, and then not again based on its assigned system ID.

[toTOW]

It's a bug introduced in v10.3.4 server software. The developer has been alerted.

[[Ars] For Caitlin]

Best I can say is check both your current log file and the older stored log files to see if you actually had processed a particular WU before. If not, then it is possible particular project(s) or server(s) could have an incorrect setting or bug. Normally the servers will only send a WU out to a particular system once, and then not again based on its assigned system ID.

Joe, sadly there's no way of knowing what the work unit is to check if it is actually one that's already been seen. Anyway, it looks like its a known problem server-side.

[toTOW]

It should be fixed.