18495, BAD_FRAME_CHECKSUM at 100%
Posted: Mon May 19, 2025 12:10 am
I was folding P18495 R38 C30 G207. At 100%, it immediately failed with BAD_FRAME_CHECKSUM. For some reason it did not dump like the v7 client would do but tried to upload the results to the server, which did not like them (maybe because wuresults_01.dat was never even created).
Most cases of BAD_FRAME_CHECKSUM happen when trying to resume from an improper restart of a core that causes data files to become corrupt, but this WU was never restarted improperly.
The server has not logged it as failed, so it is just hanging there in limbo, waiting to expire. I do not have a copy of the wudata_01.dat or I would try to fold it again from the beginning.
Most cases of BAD_FRAME_CHECKSUM happen when trying to resume from an improper restart of a core that causes data files to become corrupt, but this WU was never restarted improperly.
Code: Select all
14:05:51:I1:WU538:Completed 4900000 out of 5000000 steps (98%)
14:12:17:I1:WU538:Completed 4950000 out of 5000000 steps (99%)
14:19:17:I1:WU538:Completed 5000000 out of 5000000 steps (100%)
14:19:17:E :WU538:Core returned BAD_FRAME_CHECKSUM (112)
14:19:17:I1:WU538:Uploading WU results
14:19:17:I1:OUT17:> CONNECT vav21.fah.temple.edu:443 HTTP/1.1
14:19:17:I1:WU538:UPLOAD 100% 77B of 77B
14:19:18:I1:OUT17:> POST https://vav21.fah.temple.edu/api/results HTTP/1.1
14:19:20:E :OUT17:HTTP_NOT_ACCEPTABLE: {"error":{"message":"Quit","code":406}}