Error 11 on version 22.6 -- what to do?

only_human · 2003-09-03, 20:10

Today upon communicating with the PrimeNet server, I got "Error 11: Exponent already tested."
Strangely, it seems that my machine is retesting an exponent it already sent in the results for. Currently my machine is 61 percent into LL testing M19653323 again.

I assume that if I let my machine complete the LL test again, it will be used as a double check. I am not sure if that is true (or should be) for the same machine posting the same result twice. Should I just let it run, and how might it have happened?

(system details follow)
I move to version 22.6 on August 3rd right after sending in the results of M20165671. My machine sent results for M19653323 (the first time) on Aug 16th. My expected date to complete LL testing on M19653323 (again) is September 13th.

My worktodo.ini file is unchanged from Aug 3rd:
Test=19653323,66,1
Test=15017411,65,1
Test=20165671,66,1

The only entries in my prime.ini file that might not be typical are:
DaysOfWork=30
DiskWriteTime=1200
SequentialWorkToDo=0

Here is my recent prime.log history:
[Sun Aug 03 20:09:00 2003 - ver 23.5]
Sending text message to server:
UID: only_human/bitcruncher, M20165671 completed P-1, B1=240000, B2=5040000, WZ1: 09859AFC
Sending result to server for exponent 20165671
[Wed Aug 06 04:48:36 2003 - ver 23.6]
Updating computer information on the server
Sending expected completion date for M19653323: Aug 17 2003
Sending expected completion date for M15017411: Sep 01 2003
Sending expected completion date for M20165671: Sep 28 2003
[Sat Aug 16 10:33:50 2003 - ver 23.6]
Sending result to server for exponent 19653323
Sending text message to server:
UID: only_human/bitcruncher, M19653323 is not prime. Res64: 201E1455CC68E395. WZ1: 4428B4E4,7146808,00000000
[Wed Sep 03 11:21:47 2003 - ver 23.6]
Updating computer information on the server
Sending expected completion date for M19653323: Sep 14 2003
ERROR 11: Exponent already tested.
Sending expected completion date for M15017411: Sep 29 2003
Sending expected completion date for M20165671: Oct 26 2003

Appologies offered for the size of this message. I wanted to be complete in case it is early notice of a possible software problem.

nomadicus · 2003-09-03, 20:13

Make sure *all* your files are writeabe. I had a results.txt file (and others) accidentally set to read-only and LL'd the number 3 times.

only_human · 2003-09-03, 20:29

I just checked. That was a good suggestion...alas every file in my Prime95 directory is writeable.

Prime95 · 2003-09-03, 20:58

Did system restore overwrite worktodo.ini with an older version?

only_human · 2003-09-03, 22:19

I feel you must be right. I enabled system restore on my machine 8/15/03. At 10:06 p.m. on 8/16/03, I actually used it. I was messing around with all my network software in the wake of concerns about the latest virus flavor and wanted an easy fallback.

My results.txt file was updated at 10:33 a.m. on 8/16/03.
It seems only natural that the worktodo.ini file would be updated at the same time. However my current worktodo.ini file was last modified on 8/03/03.

I haven't sleuthed around enough yet to actually confirm that the worktodo.ini file was overwritten with an old one but it must be so.

Such a straightforward explanation and it never even occurred to me. Thank you for your attention.

GP2 · 2003-09-14, 21:42

The continuation of this thread has now been moved to the new Data forum.

2003-09-03, 20:10	#1
only_human "Gang aft agley" Sep 2002 2×1,877 Posts	Error 11 on version 22.6 -- what to do? Today upon communicating with the PrimeNet server, I got "Error 11: Exponent already tested." Strangely, it seems that my machine is retesting an exponent it already sent in the results for. Currently my machine is 61 percent into LL testing M19653323 again. I assume that if I let my machine complete the LL test again, it will be used as a double check. I am not sure if that is true (or should be) for the same machine posting the same result twice. Should I just let it run, and how might it have happened? (system details follow) I move to version 22.6 on August 3rd right after sending in the results of M20165671. My machine sent results for M19653323 (the first time) on Aug 16th. My expected date to complete LL testing on M19653323 (again) is September 13th. My worktodo.ini file is unchanged from Aug 3rd: Test=19653323,66,1 Test=15017411,65,1 Test=20165671,66,1 The only entries in my prime.ini file that might not be typical are: DaysOfWork=30 DiskWriteTime=1200 SequentialWorkToDo=0 Here is my recent prime.log history: [Sun Aug 03 20:09:00 2003 - ver 23.5] Sending text message to server: UID: only_human/bitcruncher, M20165671 completed P-1, B1=240000, B2=5040000, WZ1: 09859AFC Sending result to server for exponent 20165671 [Wed Aug 06 04:48:36 2003 - ver 23.6] Updating computer information on the server Sending expected completion date for M19653323: Aug 17 2003 Sending expected completion date for M15017411: Sep 01 2003 Sending expected completion date for M20165671: Sep 28 2003 [Sat Aug 16 10:33:50 2003 - ver 23.6] Sending result to server for exponent 19653323 Sending text message to server: UID: only_human/bitcruncher, M19653323 is not prime. Res64: 201E1455CC68E395. WZ1: 4428B4E4,7146808,00000000 [Wed Sep 03 11:21:47 2003 - ver 23.6] Updating computer information on the server Sending expected completion date for M19653323: Sep 14 2003 ERROR 11: Exponent already tested. Sending expected completion date for M15017411: Sep 29 2003 Sending expected completion date for M20165671: Oct 26 2003 Appologies offered for the size of this message. I wanted to be complete in case it is early notice of a possible software problem.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Error compiling version 29.1 on Arch Linux	graysky	Software	5	2017-03-22 18:20
ERROR: cudaGetLastError() returned 30: unknown error	garo	GPU Computing	10	2013-04-27 19:01
Error 5 causes userid change and error 17 updates for exponents	Old man PrimeNet	PrimeNet	0	2006-02-05 02:27
Prime95 Version 24.13 Error Writing Files	RMAC9.5	Software	2	2005-12-05 08:20
ERROR: Primenet error 2252. Q: which tcp/ip ports are being used for the transfer?	nevillednz	PrimeNet	15	2004-05-17 23:08

2003-09-03, 20:13	#2
nomadicus Jan 2003 North Carolina 366₈ Posts	Make sure all your files are writeabe. I had a results.txt file (and others) accidentally set to read-only and LL'd the number 3 times.

2003-09-03, 20:29	#3
only_human "Gang aft agley" Sep 2002 3754₁₀ Posts	I just checked. That was a good suggestion...alas every file in my Prime95 directory is writeable.

2003-09-03, 20:58	#4
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 3⁵·31 Posts	Did system restore overwrite worktodo.ini with an older version?

2003-09-03, 22:19	#5
only_human "Gang aft agley" Sep 2002 EAA₁₆ Posts	I feel you must be right. I enabled system restore on my machine 8/15/03. At 10:06 p.m. on 8/16/03, I actually used it. I was messing around with all my network software in the wake of concerns about the latest virus flavor and wanted an easy fallback. My results.txt file was updated at 10:33 a.m. on 8/16/03. It seems only natural that the worktodo.ini file would be updated at the same time. However my current worktodo.ini file was last modified on 8/03/03. I haven't sleuthed around enough yet to actually confirm that the worktodo.ini file was overwritten with an old one but it must be so. Such a straightforward explanation and it never even occurred to me. Thank you for your attention.

2003-09-14, 21:42	#6
GP2 Sep 2003 5×11×47 Posts	The continuation of this thread has now been moved to the new Data forum.