Added 88427 : 717*2^682046-1 (205320 digits)

Added 88442 : 609*2^683212-1 (205671 digits)

Added 88449 : 663*2^684374-1 (206020 digits)

Added 88465 : 497*2^688852-1 (207368 digits)

635*2^685706-1 is prime

777*2^686718-1 is prime

found on G8000
327*2^869829-1 is prime!

no notification and not listed there yet (more than an hour ago!)

PS:
it's the last (!) entry in the latest complete resultfile
[url]http://nplb-gb1.no-ip.org/llrnet/results/results_20090528_0001_GB_nplb_8000.txt[/url]

this prime is also not listed in the allover primes for this port here
[url]http://nplb-gb1.no-ip.org/llrnet/primes_8000.txt[/url]

where is the issue?

Nice prime!

I see that the prime was found at 00:00:21 my time; 54 minutes ago. We'll give it until after 1 AM to see if the notification gets sent out and that it gets listed in the primes log since those are done once/hour. If not, then there is a bug and I'll have Max look into it.


Gary

[quote=kar_bon;175039]found on G8000
327*2^869829-1 is prime!

no notification and not listed there yet (more than an hour ago!)

PS:
it's the last (!) entry in the latest complete resultfile
[URL]http://nplb-gb1.no-ip.org/llrnet/results/results_20090528_0001_GB_nplb_8000.txt[/URL]

this prime is also not listed in the allover primes for this port here
[URL]http://nplb-gb1.no-ip.org/llrnet/primes_8000.txt[/URL]

where is the issue?[/quote]


Max, this does indeed seem to be a problem.

Prime 327*2^869829-1 was found on May 28th at 00:00:21 CDT (my time) but showed up in the May 27th results file as the last result. Apparently this caused it to not show up in the primes.log file and no prime notification was sent. It is now May 28th at 01:12 CDT so I've given it an hour to correct itself due to the strange timing of things but it did not do so.

Can you look into and correct the problem?


Thanks,
Gary

if it is a script problem, David should also check his ports, too!

Hmm, that is very odd. Theoretically, though, no matter what the timestamp on the file, the DB should still import all k/n pairs within it. It should contain the entire contents of that file, including the prime.

I think I know why it didn't show up in the primes file for port 8000; I'll fix that and add it manually. Meanwhile, Dave, do you have any idea why the DB didn't send out a notification for it? Since it doesn't show up in the DB's prime list, it would appear that it didn't even make it into the DB. I presume the DB *is* still importing both the end-of-day results files and the intermediate ones, correct?