After over nine hours on this WU, this was the result -
17:20:06:WU01:FS00:0xa7:Folding@home Core Shutdown: FINISHED_UNIT
17:20:06:WU01:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
17:20:06:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:16506 run:0 clone:1964 gen:128 core:0xa7 unit:0x0000009c8f59f36f5eae4e836c78b234
17:20:06:WU01:FS00:Uploading 7.00MiB to 143.89.243.111
17:20:06:WU01:FS00:Connecting to 143.89.243.111:8080
17:20:12:WU01:FS00:Upload 24.09%
17:20:18:WU01:FS00:Upload 52.64%
17:20:24:WU01:FS00:Upload 82.09%
17:20:28:WU01:FS00:Upload complete
17:20:28:WU01:FS00:Server responded WORK_QUIT (404)
17:20:28:WARNING:WU01:FS00:Server did not like results, dumping
17:20:28:WU01:FS00:Cleaning up
Any thoughts?
143.89.243.111 - "Server did not like results, dumping"
Moderators: Site Moderators, FAHC Science Team
-
comixgoddess
- Posts: 87
- Joined: Wed Apr 08, 2020 9:57 pm
- Location: Pacific Northwest
-
Joe_H
- Site Admin
- Posts: 8078
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Studio M1 Max 32 GB smp6
Mac Hack i7-7700K 48 GB smp4 - Location: W. MA
Re: 143.89.243.111 - "Server did not like results, dumping"
There are several main possible causes, but not enough here to distinguish which applies. First would be if any of the output files packed up into the finished WU before the FINISHED_UNIT message is issued was corrupted or less likely missing. The check done by the server at upload time would detect that and dump the WU.
An error during the upload will have the same result.
Finally, a configuration error on the server can also result in a WU return being rejected with this error. This is harder to diagnose, it usually takes multiple reports to detect a pattern that can be looked into.
An error during the upload will have the same result.
Finally, a configuration error on the server can also result in a WU return being rejected with this error. This is harder to diagnose, it usually takes multiple reports to detect a pattern that can be looked into.