View Single Post
Old 2020-01-08, 05:48   #1
scan80269
 
"Sam"
Jun 2019
California, USA

111102 Posts
Default Missing GHz-Day credit for a completed exponent

One of my Prime95 systems completed a PRP run for an exponent (actual value renamed to M90907xxx) earlier today but apparently it did not receive any computation credit for this exponent.

Checking this exponent manually shows the correct final residue already logged into primenet with my username, but the exponent did not make it into the list of my results, and no GHz-Day credits were issued.

I noticed the following lines in prime.log:

[Tue Jan 07 05:29:32 2020 - ver 29.8]
Sending interim residue 85000000 for M90907xxx
[Tue Jan 07 09:13:35 2020 - ver 29.8]
Sending interim residue 90000000 for M90907xxx
Sending result to server: UID: scan80269/Viki5960X, M90907xxx is not prime. RES64: 9311F622F4B2E8xx. Wh4: AA99B633,35523524,00000000, AID: 76E384A4EB3DF6FD0209534E5204250B

CURL library error: Operation timed out after 180 seconds with 0 bytes received
[Tue Jan 07 10:15:33 2020 - ver 29.8]
Sending result to server: UID: scan80269/Viki5960X, M90907xxx is not prime. RES64: 9311F622F4B2E8xx. Wh4: AA99B633,35523524,00000000, AID: 76E384A4EB3DF6FD0209534E5204250B

PrimeNet error 40: No assignment
This computer has already sent in this PRP result for M90907xxx


An attempt to manually check in this exponent resulted in:

Error code: 40, error text: Another computer has already reported this PRP result for M90907xxx

As far as I can tell, that "Another computer" is my system that completed the PRP run for this exponent.

Any idea what the problem is here?

Last fiddled with by Prime95 on 2020-01-08 at 16:39
scan80269 is offline   Reply With Quote