View Single Post
Old 2020-09-11, 19:26   #53
kriesel
 
kriesel's Avatar
 
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

37·127 Posts
Default MD5 value missing from results entry & report

Gpuowl-win v6.11-340-g41d435f on gtx1050Ti and Intel I7-8750H, M139000019 PRP with proof, approx 37 days run with no GEC errors.
Code:
2020-09-11 05:57:39 peregine/gtx1050Ti 139000019 OK 138990000  99.99%; 22954 us/it; ETA 0d 00:04; 7ab69061f3c26263 (check 9.86s)
2020-09-11 06:01:38 peregine/gtx1050Ti 139000019 OK 139000000 100.00%; 22952 us/it; ETA 0d 00:00; a6a3abfc4762a2bd (check 9.69s)
2020-09-11 06:01:39 peregine/gtx1050Ti CC 139000019 / 139000019, fd86019f31e6____
2020-09-11 06:01:39 peregine/gtx1050Ti proof: save residue @ 139000064
2020-09-11 06:01:58 peregine/gtx1050Ti 139000019 OK 139000400 100.00%; 26920 us/it; ETA 0d 00:00; c535b7cebd01e5da (check 9.78s)
2020-09-11 06:01:58 peregine/gtx1050Ti {"status":"C", "exponent":"139000019", "worktype":"PRP-3", "res64":"fd86019f31e6____", "residue-type":"1", "errors":{"gerbicz":"0"}, "fft-length":"7864320", "program":{"name":"gpuowl", "version":"v6.11-340-g41d435f"}, "user":"kriesel", "computer":"peregine/gtx1050Ti", "aid":"3061FC342941433195EA4620C419____", "timestamp":"2020-09-11 11:01:58 UTC"}
2020-09-11 06:03:26 peregine/gtx1050Ti proof: building level 1, hash 1e0f6510e0f731__
2020-09-11 06:03:28 peregine/gtx1050Ti proof: building level 2, hash 1be18d2eee5f67__
2020-09-11 06:03:32 peregine/gtx1050Ti proof: building level 3, hash 7c9434d64e1f1e__
2020-09-11 06:03:41 peregine/gtx1050Ti proof: building level 4, hash 51a1ee7f9d309d__
2020-09-11 06:03:59 peregine/gtx1050Ti proof: building level 5, hash 5393da0317b2f8__
2020-09-11 06:04:38 peregine/gtx1050Ti proof: building level 6, hash 7122dda94e1162__
2020-09-11 06:05:57 peregine/gtx1050Ti proof: building level 7, hash ed1da1557f99bb__
2020-09-11 06:08:41 peregine/gtx1050Ti proof: building level 8, hash 620c5ba7ec0fe4__
2020-09-11 06:14:05 peregine/gtx1050Ti PRP-Proof 'C:\Users\kkrie\Documents\gpuowl-v6.11-340\139000019\139000019-8.proof' generated
2020-09-11 06:14:06 peregine/gtx1050Ti worktodo.txt line ignored: "Doublecheck=181000033"
2020-09-11 06:14:06 peregine/gtx1050Ti Bye
Doublecheck should have been DoubleCheck.
Result line lacked an MD5 value, and has been reported. Log result line above also lacks it.
It looks like it did not record an MD5 when generating the proof, perhaps getting derailed by the error with the following worktodo line.
So then the PrimeNet server refuses the proof file upload for M139000019. Its MD5 does not match the null value the server has.
Using the standalone uploader:
Code:
MD5 of 139000019-8.proof is 837e4c2e3dbd438f2cbc44f6ed0e____
Proof file exponent is 139000019
Filesize of 139000019-8.proof is 156375085
Server response missing URLToUse: {"error_status":401,"error_message":"Unauthorized","error_description":"JSON result not yet submitted by your user ID or proof file MD5 mismatch"}
Remove the proof file from the worker's directory tree (it's saved on the uploader system). Reconstruct the worktodo entry. Stop LLDC (takes 5.5 minutes for Jacobi check). Retry from last saved M139M files, going up to 139000000.
Rebuilding the proof takes another 13.5 minutes.
There's still no md5 value in the results.txt line.
Is this a known issue with gpuowl-v6.11-340? Note that it outputs a result line before beginning to build the proof, so would not have an MD5 value to attach yet. And does not go back and attach or insert or log one later.
If I update to a later version and coax out an MD5 value during proof reconstruction, I won't be able to get the server to accept it, because there's already a zero offset result logged without an MD5. I doubt it would accept two result submissions for the same AID either. And I would not want it to double credit GhzDays. Nor have a proof go to waste.

Last fiddled with by kriesel on 2020-09-11 at 19:40
kriesel is online now   Reply With Quote