Automated primality testing with LLRnet for CRUS

[em99010pepe]

That is good to know. It seems to be working now. I will give it a while before ramping back up. I'm sure you realize that the higher we go in "n" value the less the load will be on the server connections, it is just a matter of time and all will smooth out.

I wasn't here but the server went down from 18:51 to 20:03 and got up by itself...

Yes, as n goes high the number gets larger and so more time is needed to process and therefore less communications between clients/server.

[tnerual]

I wasn't here but the server went down from 18:51 to 20:03 and got up by itself...

maybe it was the "pruning" job ... if llrnet is at a higher priority than llrserver, pruning job is going very slowly and server appears off during the whole time.

how to check that ? take a look at the knpairs.txt details (last modification time)

if time of knpairs.txt is around 20:03, increase priority of llrserver

[Helix_Von_Smelix]

Does anyone know how to run this from behind a proxy server??