Beyond is right, you can set up a proxy, sorry, forgot about it.
Printable View
Beyond is right, you can set up a proxy, sorry, forgot about it.
Increased number of concurrent connections to 60. Rally is under way.
First result in on port 300:
and on port 100 (draw):Quote:
user=Anonymous
[02/23/08 18:59:41]
837*2^365204-1 is not prime. Res64: 475EF4E87375EFE4 Time : 38999.0 sec.
user=Free-DC_Beyond
[02/23/08 19:00:01]
1001*2^365554-1 is not prime. Res64: 30C65979AFA98D2E Time : 169.0 sec.
user=Free-DC_Beyond
[02/23/08 19:00:02]
775*2^365547-1 is not prime. Res64: AB9DB898FF4862D2 Time : 1518.0 sec.
Quote:
user=gd_barnes
[02/23/08 18:59:55]
639*2^284613-1 is not prime. Res64: D03D672FFF1B01F0 Time : 756.0 sec.
user=Free-DC_em99010pepe
[02/23/08 19:00:03]
401*2^284650-1 is not prime. Res64: 03F684C4F1B1AF3F Time : 436.0 sec.
user=gd_barnes
[02/23/08 19:00:03]
533*2^284614-1 is not prime. Res64: C52191D6256872F1 Time : 740.0 sec.
user=ArsTechnica_BlisteringSheep
[02/23/08 19:00:05]
979*2^284555-1 is not prime. Res64: BBED63F2CBFBFEFE Time : 1693.0 sec.
If Mr. Barnes continues to have problems connecting I'll back off the rally, with 60-70 cores running I'm afraid I am flooding the server with connection request.
I pull out 6 cores from LLRnet (now manual LLR'ng the lower ranges), at least the connection is free from here to the world.
I could, but I won't. Too much work involved and too many machines, I do not use the manual LLR on my personnal prime searches, just llrnet.
I cut-off access to your server from my end....will wait till the cache is drained brfore reconnecting.
Carlos, just now uploading 4000+ results. I will attempt to download 15000+ tests to keep the machines crunching thru the night.
It did not work out, was unable to grab that many tests. Probably a good thing. I have been unable to get everything connecting to my proxy, it's being overloaded and dropping connections too.
I've pulled a few machines off to see if the proxy can catch up. If that works fine, if not that is fine too, I'm tired of messing with them, I've had enough for one day.
I think the best bet for the next time is to reserve several large ranges and split them between several llrnet servers running on my systems. :idea:
It was a good try Carlos, but your server is down again. I have 2000+ results (as of now) ready to upload when you come back online. :Pokes::cheers:
Ok, going to try to get a proxy server running.
If all works out well, I may open it to the outside.
Well I'm completely out of work, but still a boat load of results to be uploaded. Going to bed and will worry about it tomorrow.
It's spotty at best. I got lucky, managed to get my proxy server up (thanks!) and snagged 100 just to keep my 8 cores busy for a little bit and see how it works out.
I have 4gb of ram so that's a non-issue.
Now Carlos can't blame me for crashing his port 100 server :p ;) :D
The rally is off, I'm tired of all this stupid server. 19c2c462 client is stalling the server...
Clients connected on server port 100 are:
22489c1 and 200a8c0 Free-DC_em99010pepe
829ea741 gd_barnes
75242c52 Flatlander
ee651e4c Free-DC_Beyond
b6ccb9d8 XtremeSystems_glennpat
5498c850 Free-DC_tnerual
Server is up and running.
19c2c462 is you Beyond, must be one of your clients, I suspect the proxy server...lol
We need to find a way to minimize the traffic load...
It's Alive! Work is flowing again. :cheers:
Hang in there Carlos, we will get the lower ranges knocked out. :)
I was trying to just start up a few at a time to keep from flooding the server this morning. It does not seem to be working. even though I got a bunch of results uploaded and a few tests downloaded it has locked up again.
I'm going to clear the caches on all the clients while I have access cut off to your server, then shut the clients down. At that point I will open access to your server again to upload the results.
Sorry for all the problems caused, I would have never dreamed llrnet could not handle the load. :(
Beyond,
Tnerual pointed me something useful that I though I already had. Microsoft introduced Win XP SP2 and limited the number of possible TCP connection attempts per second to 10 (from unlimited in SP1). I applied http://www.lvllord.de/ patch and increased that number to 100.
More info in here.
I hope now the server can handle more connections per second. It's XP SP2 limitation and not llrnet one.
Carlos
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.
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
Does anyone know how to run this from behind a proxy server??
:cheers: