CRUS LLRnet server discussion

[gd_barnes]

Originally Posted by Anonymous

Well, I guess we could do that...but since at the moment, Sierp. is the higher priority (it's getting less attention from the manual LLRers), we'll want that one on port 443, since port 443 can be accessed through corporate firewalls usually. Then the Riesel one can go on port 444.

As for keeping the Riesel one busy: How about you let it run dry first, after inserting the doublecheck work, then after the residuals have been verified, you can insert more Riesel work that I'll be giving you. What do you think?

And I guess we would need another server for Sierp base 6 assuming that we opt to go that route for team drive #3.

[em99010pepe]

For the moment I am worried about the rejected numbers I am receiving...I was playing around with the server set up....I am manually re-introducing them on the knpairs.txt.

[mdettweiler]

Originally Posted by gd_barnes

And I guess we would need another server for Sierp base 6 assuming that we opt to go that route for team drive #3.

Yeah, we could do that easily, too.

[mdettweiler]

Originally Posted by em99010pepe

For the moment I am worried about the rejected numbers I am receiving...I was playing around with the server set up....I am manually re-introducing them on the knpairs.txt.

Rejected numbers? What rejected numbers?

[em99010pepe]

user=Anonymous
[01/22/08 21:27:45]
33863*2^354920-1 is not prime.  Res64: AC69EDD57B179CDA  Time : 0.0 sec.
user=em99010pepe
[01/22/08 21:31:36]
21555*2^354928-1 is not prime.  Res64: FE1D28ADDB5D9D4F  Time : 673.0 sec.
user=tnerual
[01/22/08 21:35:17]
13703*2^354932-1 is not prime.  Res64: ECA298A7B7D5C228  Time : 794.0 sec.
user=kar_bon
[01/22/08 21:38:56]
33023*2^354936-1 is not prime.  Res64: 19215EC30929D35C  Time : 853.0 sec.

I was playing with the prune and the maximum allowed time for a user to complete a job so I got a few rejected numbers, not to worried about, everything is under control.

[mdettweiler]

Originally Posted by em99010pepe

user=Anonymous
[01/22/08 21:27:45]
33863*2^354920-1 is not prime. Res64: AC69EDD57B179CDA Time : 0.0 sec.
user=em99010pepe
[01/22/08 21:31:36]
21555*2^354928-1 is not prime. Res64: FE1D28ADDB5D9D4F Time : 673.0 sec.
user=tnerual
[01/22/08 21:35:17]
13703*2^354932-1 is not prime. Res64: ECA298A7B7D5C228 Time : 794.0 sec.
user=kar_bon
[01/22/08 21:38:56]
33023*2^354936-1 is not prime. Res64: 19215EC30929D35C Time : 853.0 sec.

So you're saying that those were accidentally received on the Sierpinski server?

How about you just leave the Riesel server on port 443, and the Sierpinski on port 444, until we've run the Riesel server dry?

[em99010pepe]

Originally Posted by Anonymous

So you're saying that those were accidentally received on the Sierpinski server?

How about you just leave the Riesel server on port 443, and the Sierpinski on port 444, until we've run the Riesel server dry?

No, they were received on the Riesel server....Now everything is back to normal.
We will make as I suggested, two server, two different ports.

[mdettweiler]

Originally Posted by em99010pepe

No, they were received on the Riesel server....Now everything is back to normal.
We will make as I suggested, two server, two different ports.

Okay. So, let me see if I've got this straight: you're going to keep the Riesel server on port 443 until it's run dry, with the Sierp. server on port 444. When the Riesel server has run dry, you'll shut it down, move the Sierp. server to port 443, then once I've verified the doublecheck residuals, I'll send you more files for the Riesel server, and you'll start it back up on port 444. Correct?

[em99010pepe]

One thing I need to clarify. I can't shutdown the Riesel server because there's a time limit for receiving the work from the clients. Imagine someone just shutdowns a client with 10 numbers to test. Those 10 numbers will only be again available to distribute when the server receives an answer from that client within the time limited imposed by the server. So I can't change the ports between servers...

[em99010pepe]

Originally Posted by Anonymous

Okay. So, let me see if I've got this straight: you're going to keep the Riesel server on port 443 until it's run dry, with the Sierp. server on port 444. When the Riesel server has run dry, you'll shut it down, move the Sierp. server to port 443, then once I've verified the doublecheck residuals, I'll send you more files for the Riesel server, and you'll start it back up on port 444. Correct?

I won't change the ports. I only can do that when all servers dry out....The Riesel one will take at least more 24 hours...

[mdettweiler]

Originally Posted by em99010pepe

One thing I need to clarify. I can't shutdown the Riesel server because there's a time limit for receiving the work from the clients. Imagine someone just shutdowns a client with 10 numbers to test. Those 10 numbers will only be again available to distribute when the server receives an answer from that client within the time limited imposed by the server. So I can't change the ports between servers...

Okay, then: Did anyone send in any results for the Sierp. server yet? If not, then would you please shut it down for the time being? That way, we can hold off until we can start it on port 443.