Automated primality testing with LLRnet for CRUS

[Beyond]

Thank you.
I'm sorry but the server went down at 2 am here and I went to bed at 1 am ...

I noticed ..... no problem, I had already pulled 1000+ exponents for my proxy.

Im noticing a lot of "server refused your new result" error messages

[em99010pepe]

I noticed ..... no problem, I had already pulled 1000+ exponents for my proxy.

I'm noticing a lot of "server refused your new result" error messages

Don't worry, they will be re-assigned but for the last 3 hours I received only one rejected pair on port 300 and 9 on port 100 where 6 were from you. That's normal, it's because I tried to put the server online for several times...

The client idles connections when it can't connect and tries again to connect every 1 min or so, the server will get all results. So far on more than 500 000 k/n pairs we had two misses.

[alpha]

Should port 300 still work? Mine has seized up.

[em99010pepe]

Should port 300 still work? Mine has seized up.

Yep. Your last result was at:
user=Free-DC_alpha
[02/23/08 11:06:33]

It's 12:21 here...what's your cache size?

[alpha]

Restarted the client and it is working again now.

Cache size is just the default of 10. Doesn't really matter because I'm running it alongside dnet. For most of the time I've contributed to this it has only been half a core but I gave it a full core overnight last night.

[em99010pepe]

Restarted the client and it is working again now.

Cache size is just the default of 10. Doesn't really matter because I'm running it alongside dnet. For most of the time I've contributed to this it has only been half a core but I gave it a full core overnight last night.

Ok. Got 5 results from you.

[em99010pepe]

Ironbits,

Please check all your cores running on server port 100. Last contact before the server went down was from one of your machines. A few years ago RieselSieve had a similar problem and it was a faulty client that jammed the server.

Thank you.

Carlos