server / stats maintenance

All,

The SB server will be unavailable for about 20-30 minutes this evening. Shortly afterwards I'll begin making some changes to the web statistics engine. The website will stay up, but you may notice (very) odd behavior from the "range stats," test expiration pages and factor submission pages. I'm not sure how long it'll take to finish the changes but I expect to have everything done this evening.

We're overhauling the mechanism the server uses to assign tests to clients. For now, the assignment behavior will remain the same, but the overhaul will allow us much greater control over assignment patterns in the future.

The server is now back online. Statistics on the website may behave strangely for the next few hours.

Everything is done, for the moment.

Some statistics have been changed or removed; some temporarily, others permanently. I'll explain this in more detail tomorrow, being short on time at the moment.

Most notably, the following page, which used to show the statistics for the k ranges tested by "secret" and "supersecret," is totally different. It now shows the status (updated every 15 minutes) of the server's new internal assignment queues. Again, I'll go into more detail on this later. For now, I hope it is at least partially self-explanatory.

http://www.seventeenorbust.com/secret/

do you plan to create some special accounts from this list?

dropped-tests
error-fix
first-pass
garbage
largest-prime
missing-tests
residue-recovery
second-pass

Are the any maintenance on the server?

I ask this because the server is not responding. DNS is ok.

at around 2am PST, my clients died, and didn't re-start.
I started new clients, then noted the old ones were still there in the ps -aef list, so killed off the old idle/zombie? clients.
They appear to be running again.
:Pokes: what happened, and why didn't the clients re-start themselves?

I have the same problem! My production graph shows a sudden steep drop off!

From my sclient.log, as you can see the client seems to stop running after "Opening connection". The next time it runs is when I notice it's not running and kill and restart the process.

Quote:

---

[Thu Jan 27 09:21:53 2005] n.high = 6060820 . 304 blocks left in test
[Thu Jan 27 10:09:27 2005] resolving hostname
[Thu Jan 27 10:09:41 2005] opening connection
[Thu Jan 27 14:21:29 2005] client process [v2.3.0] invoked
[Thu Jan 27 14:21:29 2005] priority set to idle
[Thu Jan 27 14:21:29 2005] got k and n from cache
[Thu Jan 27 14:21:29 2005] AMD Athlon(tm) XP 3000+ detected. Enabling cpu specific optimizations.
[Thu Jan 27 14:21:30 2005] restarting proth test from cache (k=10223, n=7434377) [81.6%]
[Thu Jan 27 14:21:41 2005] resolving hostname
[Thu Jan 27 14:21:42 2005] opening connection
[Thu Jan 27 17:26:52 2005] client process [v2.3.0] invoked
[Thu Jan 27 17:26:52 2005] priority set to idle
[Thu Jan 27 17:26:52 2005] got k and n from cache
[Thu Jan 27 17:26:52 2005] AMD Athlon(tm) XP 3000+ detected. Enabling cpu specific optimizations.
[Thu Jan 27 17:26:53 2005] restarting proth test from cache (k=10223, n=7434377) [81.6%]

---

You might try running through an SBQueue. It seems to be able to fetch just fine.:cool:

Apparently something did go awry early this morning, but I have no idea what or why. Everything seems fine now. I'll ask Mike...

Mike reports the hardware was fine, but the server process had somehow frozen. He had to kill & restart it that morning. It's been a long time since anything like that has happened and I have no idea what went wrong. Maybe just a fluke... we'll keep an eye on it in case it happens again =(

Thanks for reporting it...