Okay, looks like restarting cron did the trick! I see that the status page updated correctly at 02:00 CDT. Hopefully the status page script will do the same in turn tomorrow night. :smile:

Thanks IB for the tip! :tu:

[QUOTE] Hopefully the status page script will do the same in turn tomorrow night. :smile:
[/QUOTE]

Sorry, it didn't.

[quote=MyDogBuster;175640]Sorry, it didn't.[/quote]
Ergh! This is driving me bonkers.

I'll try rebuilding the crontab from scratch--maybe that will do the trick.

I'll move a couple of quads from port 5000 to 9000 to get the 9th drive finished off and so that we can get on to pushing the 6 k's from the individual-k drive a little higher.

GB-servers are STILL not rolling over. I'm not sure whether this is a cron problem, or just an issue with the Perl script. I'll try reverting to the old version of the Perl script (which still has the 1-minute bug in it, but I'll monitor things to make sure that it doesn't manifest itself) to see if that helps.

Port 9000 has officially handed out and completed the last pair for k=1400-2000 and n=200K-350. Nice work all!! :wacky: It's nice to be done with that non-top 5000 range.

Amazingly there are no straggling pairs to process so the range can be considered unofficially complete pending final verification of results and primes for k=1800-2000. Once verified, all k=1400-2000 will be fully complete to n=650K! :smile: (k=1000-1400 is still only considered to be at n=500K pending receiving results from Peter Benson for n=500K-600K, which I think is close to completion now.)

Port 9000 is now handing out work for 6 k's in the k=350-370 range for n=700K-800K. I will personally leave 2 quads on it for a while since those 6 k's are at the lowest search level of any k<400 now.

With the new range now top-5000, I have sent a PM to the Dave's asking them to turn the Email notification of primes back on for the port. In the mean time, if you are running clients on the server, you might do a daily glance at the bottom of our prime.txt file for the server [URL="http://nplb.ironbits.net/primes_9000.txt"]here[/URL] to see if you have any primes.


Gary

[quote=gd_barnes;176245]With the new range now top-5000, I have sent a PM to the Dave's asking them to turn the Email notification of primes back on for the port. In the mean time, if you are running clients on the server, you might do a daily glance at the bottom of our prime.txt file for the server [URL="http://nplb.ironbits.net/primes_9000.txt"]here[/URL] to see if you have any primes.[/quote]
Actually, you can do that from the web interface: log in to the Admin page, and click "Manage Mailer". :smile: (Meanwhile, I've turned email notification back on for IB9000.)

I just had a 30 second power blip. I've got my server machine restarted and am now going through Max's instructions to restart the servers.

If you're connected to one of my servers, you might check your machines in ~30 mins. to make sure that they are receiving pairs.

I'll edit this post when all of the servers are officially restarted.

BTW, does anyone know how much a battery backup for just one machine would cost? Showing my ignorance there...I'm assuming that if I got a backup, it could handle multiple machines; although it's capacity would make a difference.

Most of my power blips are < 1 minute...just enough to cause me great headaches; mainly on the server machine.

Edit: I have now restarted all of the servers. Max, you might check Crunchford to make sure I did everything right. Port G4000 started proposing pairs to Ian and port G8000 started proposing a pair to Vaughan. I didn't see any activity on the PRPnet servers. BTW, excellent instructions and I leared a better way to do the terminal windows now. :-)



Gary

Somethings still not right. I can't connect.

EDIT: 8000 seems to be running, 4000 isn't

That's odd. It just stopped itself after doing (what it appears to be) it's hourly pruning process. I just now started it again. It's now proposing pairs to you again.

It's right before the hour now so I'll watch it do its pruning process and make sure it keeps going this time.

Edit: It didn't do the pruning right on the hour; perhaps because it was right near the hour when I restarted it. It still appears to be sending pairs OK now.

I also checked port 8000 and the two PRPnet ports. Port 8000 looks good. PRPnet port 2000 appears to have properly sent some pairs and received some residues from Max.

I'll check it every 30 mins. or so for a while.

[url]http://www.newegg.com/store/SubCategory.aspx?SubCategory=72[/url]