Primenet error 30: CPU not registered

[Jud McCranie]

I ran GIMPS for 8 years or so, then about 2 years ago I switched to Seventeen or Bust. Right now I have three computers each running four instances of Prime95. About a day ago, one one of the computers I've been using for about 2-3 years, I started getting the message:

Primenet error 30: CPU not registered
ERROR_UNREGISTERED_CPU
retry count exceeded

It tries again in 70 minutes; gets the same thing.

The other two computers don't have this problem. What is the problem and how can it be fixed?

[Prime95]

Good question. I'm guessing that for some reason prime95 has forgotten its UID. This can legitimately happen if prime95 thinks it might be running on a new computer (significantly different hardware specs or OS specs), or it can happen due to bugs in prime95 or corrupt files.

You might try replacing prime.txt and local.txt with a backup from a few weeks ago.

You might try creating a new folder with a default install of the SoB client. Let it register as a new computer, then copy over the old prime.spl and merge the worktodo.txt files and copy over any save files. I'm not sure if this will work as I'm not familiar with the SoB server.

[Mark Rose]

For what it's worth, I've never had trouble moving assignments in worktodo.txt, save files, and even local.txt between computers with SoB. I've even accidentally run the exact same local.txt on multiple computers at the same time and it's worked. The SoB server doesn't seem very picky.

[Jud McCranie]

I have old prime.txt and local.txt files. Will replacing them cause me to lose work, or cause me to lose credit for work done?

[Mark Rose]

Originally Posted by Jud McCranie

I have old prime.txt and local.txt files. Will replacing them cause me to lose work, or cause me to lose credit for work done?

Nothing in local.txt matters. In prime.txt, only two things are important:

V5UserID=YOUR_SOB_USERNAME

And set MersenneIP in the PrimeNet section:

[PrimeNet]
MersenneIP=www.seventeenorbust.com

All the work is stored in results.txt, worktodo.txt, and the various pNNNNN_MMMMMMMM* files.

[Jud McCranie]

[QUOTE=Mark Rose;388302]Nothing in local.txt matters. In prime.txt, only two things are important:

V5UserID=YOUR_SOB_USERNAME

And set MersenneIP in the PrimeNet section:

[PrimeNet]
MersenneIP=www.seventeenorbust.com

The user ID is OK. The MersenneIP is

MersenneIP=sb.pns.net


but that is the same thing as it was over 2 years ago. And at least one of the computers that is working has the same thing.

The local.txt file has changed quite a bit (should I change the ComputerGUID back to the old one?

======================
current local.txt
------------------
OldCpuSpeed=3392
NewCpuSpeedCount=0
NewCpuSpeed=0
RollingAverage=901
RollingAverageIsFromV27=1
ComputerGUID=54d46c7514257fc78615fae26abef2c9
ComputerID=
SrvrP00=10
LastEndDatesSent=1416712128
RollingHash=1927776584
RollingStartTime=1416749316
RollingCompleteTime=465843
Affinity=100
ThreadsPerTest=1

=================================

Old local.txt
----------------
OldCpuSpeed=3536
ComputerGUID=cb0c499ac25136d5765b3a621d3c2387
SrvrUID=928561183
ComputerID=
SrvrComputerName=2075700499
SrvrPO1=0
SrvrPO2=1
SrvrPO3=13
SrvrPO4=256
SrvrPO5=256
SrvrPO6=630
SrvrPO7=90
SrvrPO8=1
SrvrPO9=4
SrvrP00=7
LastEndDatesSent=1339943774
Memory=256 during 10:30-1:30 else 256
Affinity=100
ThreadsPerTest=2
RollingHash=-366051531
RollingStartTime=1339964849
RollingCompleteTime=788799
RollingAverage=1025
NewCpuSpeedCount=0
NewCpuSpeed=0
RollingAverageIsFromV27=1
AffinityScramble2=01234567

[Mark Rose]

www.seventeenorbust.com and sob.pns.net both resolve to the same ip, 69.9.160.186. I guess either works!

[Prime95]

Originally Posted by Jud McCranie

The local.txt file has changed quite a bit (should I change the ComputerGUID back to the old one?

Make a backup, then try it.

[Jud McCranie]

Originally Posted by Prime95

Make a backup, then try it.

OK, I thought the safest thing to do was to make a complete backup of the folder, download the zip file from 17 or bust, unzip it to the same folder, overwriting anything that exists, and update prime.txt. I still get the same error. (I also get it if I do manual communication.)

I don't know if this means anything, but it says "retry count exceeded".

I had 10 instances running on 3 computers, with exponents in the 29,000,000 range. About 2 weeks ago I discovered that I was assigned an exponent under 10,000,000! I wanted more of those - I figured they had just been released! I can do one of them in a day or day and a half, rather than 7-8 days - and they are more likely to be prime.

I added 8 more instances to grab all of the small exponents I could. I had been making changes to my WorkToDo file to move the 29,000,000 ones to the bottom. Then a day or two ago I decided to "expire" the 29-million exponents. That is about when the problem started on this computer. During that period I did a lot of manual communication to get small exponents.

Could that have anything to do with the problem?

=====
added

Or maybe I should start with a new, empty folder, unzip to there, and copy the necessary data files over?

[Prime95]

We're just trying things til we find something that works....

1) Try deleting the prime.spl file. It may have some malformed messages in there.

2) Yes, try a fresh install in a new directory only copying the minimum necessary files.

[Jud McCranie]

I stopped P95, exited, renamed prime.spl and restarted and that seems to have worked. It communicated with the server and sent a bunch of completion dates, and I don't see the error message.

Thanks for all of the help!

PS - it did not make a new prime.spl file. Is that OK?