OK, I'm screwed guys. I was correct, Carlos. The server will not allow any more connections. Here is the message that I'm getting in the console:

LLRnet-NPLB current status :
Initializing ...
LLR network client 0.9b7 started
Based on LLR version 3.5.0
Loading library 'win32' ...
winlopp thread
Running 'init.lua' ...
Loading library 'basic' ...
Loading library 'client' ...
Loading library 'fox' ...
connection request from 100007f:1516 (socket 264)
LLRMain started
server dialog thread started ...
GUI : Closing connection to all clients
connection closed (socket 264)

HELP PLEASE!!

EDIT: I've got 6 cores just waiting in sleep mode at this very moment.

[QUOTE=em99010pepe;126679]Hey Blist, you're flying!!![/QUOTE]

This new machine is pretty fast. It's showing .28-.29ms/iteration for each instance, with all 8 cores running. And once I get the 64-bit O/S on it, I'll finally be able to use all 8gigs of memory.

But the llrnet server has some :censored: bug where it won't ever send me any primes. :cry:

:alex:

[quote=gd_barnes;126680]OK, I'm screwed guys. I was correct, Carlos. The server will not allow any more connections. Here is the message that I'm getting in the console:

LLRnet-NPLB current status :
Initializing ...
LLR network client 0.9b7 started
Based on LLR version 3.5.0
Loading library 'win32' ...
winlopp thread
Running 'init.lua' ...
Loading library 'basic' ...
Loading library 'client' ...
Loading library 'fox' ...
connection request from 100007f:1516 (socket 264)
LLRMain started
server dialog thread started ...
GUI : Closing connection to all clients
connection closed (socket 264)

HELP PLEASE!!

EDIT: I've got 6 cores just waiting in sleep mode at this very moment.[/quote]
Why don't you try closing LLRnet, then starting it up again? I'm thinking that maybe your LLRnet got all confused when the server wouldn't take any more connections.

Gary, I doubled the number of concurrent connections, now is at 60.

[quote=BlisteringSheep;126682]

But the llrnet server has some :censored: bug where it won't ever send me any primes. :cry:

:alex:[/quote]

You complain too much, made an exception for you, lol:

user=ArsTechnica_BlisteringSheep
[02/23/08 19:38:32]
889*2^284685-1 is prime!

[quote=Anonymous;126683]Why don't you try closing LLRnet, then starting it up again? I'm thinking that maybe your LLRnet got all confused when the server wouldn't take any more connections.[/quote]


I've tried ending and restarting 3 times on each machine. I've tried ports 100 and 300. I've tried 1 in the cache, 5 in the cache, and 50 in the cache. You name it...it's sleep mode after 1-2 mins every time. There's nothing wrong with my internet connection and there is no firewall issue. This all worked fine last night in test.

I'm also aware that the connections were double to 60. Something's still wrong.

Can someone please stop one of their LLRnet machines, wait 30 seconds and the reconnect it? It has to be related to allowing new connections.


Gary

[quote=gd_barnes;126687]I've tried ending and restarting 3 times on each machine. I've tried ports 100 and 300. I've tried 1 in the cache, 5 in the cache, and 50 in the cache. You name it...it's sleep mode after 1-2 mins every time. There's nothing wrong with my internet connection and there is no firewall issue. This all worked fine last night in test.

I'm also aware that the connections were double to 60. Something's still wrong.

Can someone please stop one of their LLRnet machines, wait 30 seconds and the reconnect it? It has to be related to allowing new connections.


Gary[/quote]
Try rebooting your machine--maybe the network stack got overloaded or something.

The connections can't be the problem, because clients don't keep an open connection to the server--they start a new connection each time they get or report a k/n pair.

What about purging the DNS resolver cache? (/flushdns on DOS box)

EDIT:
[quote=gd_barnes;126687]
Can someone please stop one of their LLRnet machines, wait 30 seconds and the reconnect it? It has to be related to allowing new connections.
[/quote]

Done and the client reconnected, received and sent the wu.

OK, that's the only thing I haven't tried. I'll try rebooting the machines now. But why did my son's machine all of a sudden have this problem? It ran great on port 300 until 1 hour before rally time with some ups and downs due to server issues.

Rebooting all machines now...

Alright, I'm in the rally. I started it maybe 15 minutes late (7:15ish GMT) because I was a little confused about when it started, but I'm in now and have completed 20 results. I've had no problems connecting.
Or, um, has it not actually started yet? Either way, I'm on.

[quote=Mini-Geek;126691]Alright, I'm in the rally. I started it maybe 15 minutes late (7:15ish GMT) because I was a little confused about when it started, but I'm in now and have completed 20 results. I've had no problems connecting.
Or, um, has it not actually started yet? Either way, I'm on.[/quote]
Yes, the rally's started. :smile: