No luck at all after the reboots. They still all go into sleep mode after 1-2 mins.

It must be me since no one else is having issues. There's nothing left for me to try. I'm shut out on almost half my machines for the rally.

In the future, I will just start all of my machines on LLRnet 24 hours before the rally and let them run non-stop through it. Trying to sieve until 1-2 hours before the rally with my home machines and then starting LLRnet then doesn't work at all. I've had the same problem both times. But it's definitely a different issue this time. Wish I knew what it was...

I'll leave them in sleep mode for 2 more hours to see if they finally connect. If not, then it's back to sieving.


Gary

Why has the server been, apparently, having so many problems this rally? Is there too much participation for it to handle?

[quote=Mini-Geek;126694]Why has the server been, apparently, having so many problems this rally? Is there too much participation for it to handle?[/quote]
Sort of. 4 servers is a lot to run on one machine with only 1 GB of RAM, so when some of them go under heavy load like right now, you have problems. That's why we're hoping to clean up the port 100 server so it can be shut down.

Hey Gary, I was just thinking...maybe your problem is the same as it was last rally. :wink:
[quote=gd_barnes;125322]OK, guys. We've got lift off! After losing 2+ hours, all 7 cores are running LLRnet. :flex::rolleyes::blush:

After getting a PM from Karsten, I tried one last thing. Instead of double-clicking on llrnet.exe, I right clicked and hit open. It worked on all 4 cores of the 2 Athlons.

The connection between the GUI and executable is confusing. Sometimes LLRnet will be running but you still have to hit 'connect' on the GUI for it to 'refresh' what is happening properly.

Thanks for all of your help. Sorry about the problems. I'll check them from time to time to make sure they're still running.


Gary[/quote]

I'm off the rally, the server can't hold so many connections, it stalls every 2 hours.
I reserved 268.8 to 276.0 so I have two weeks of manual work.

I advise people who can manual LLRing to do so.

EDIT: Beyond is asking if it is necessary to pull out his 70 cores from LLRnet.

[quote=em99010pepe;126703]I'm off the rally, the server can't hold so many connections, it stalls every 2 hours.
I reserved 268.8 to 276.0 so I have two weeks of manual work.

I advise people who can manual LLRing to do so.

EDIT: Beyond is asking if it is necessary to pull out his 70 cores from LLRnet.[/quote]
I think non-server versions of Windows have their own limit on connections--so yeah, I guess the only thing we can do about that is offload one or more of the LLRnet servers onto another machine. Or you could always put Linux on the LLRnet server, I don't think it has that limit.

Gary, did you read my LLRnet tutorials I sent you yet?

[quote=Anonymous;126697]Hey Gary, I was just thinking...maybe your problem is the same as it was last rally. :wink:[/quote]

No, it was nothing to do with that. I was confused as to the difference between the GUI and LLRnet. I didn't know that the LLRnet could be running when the GUI was disconnected and I kept thinking that LLRnet was not running when it was.

BUT...see next post...

Gary, if you want you can open 315k-320k to manual reservation, I'll take that range of the server, it's your call.

[quote=em99010pepe;126703]I'm off the rally, the server can't hold so many connections, it stalls every 2 hours.
I reserved 268.8 to 276.0 so I have two weeks of manual work.

I advise people who can manual LLRing to do so.

EDIT: Beyond is asking if it is necessary to pull out his 70 cores from LLRnet.[/quote]


AH HA!!! I was right all along. It WAS the # of connections! Told you!! :smile:

You know why I know this for sure now? ALL of my machines just started up and are running beautifully now. 7 at work, 6 at home just zooming away.

And guess when this happened? About 8:50 PM GMT shortly after the time of your post and almost exactly when you pulled your machines off of it.

I bet you can't connect now like I could not connect earlier because I'm now in your way with 6 additional instances of LLRnet running. It seems that we're right at that critical limit.

I have 50 k/n pairs in all of the queues on my home machines now. Shall I continue running LLRnet on all of them? If not, I'll drop it down to 1 in the cache, run them to clear out the 50 pairs in the queues, and go back to sieving.


Gary

[quote=gd_barnes;126712]AH HA!!! I was right all along. It WAS the # of connections! Told you!! :smile:

You know why I know this for sure now? ALL of my machines just started up and are running beautifully now. 7 at work, 6 at home just zooming away.

And guess when this happened? About 8:50 PM GMT shortly after the time of your post and almost exactly when you pulled your machines off of it.

I bet you can't connect now like I could not connect earlier because I'm now in your way with 6 additional instances of LLRnet running. It seems that we're right at that critical limit.

I have 50 k/n pairs in all of the queues on my home machines now. Shall I continue running LLRnet on all of them? If not, I'll drop the queues to 1, run them to clear out the queues, and go back to sieving.


Gary[/quote]
Yes, that's it--Windows XP's 10-connection limit. Thus, even if you set LLRnet to allow more, XP still gets in the way.

As I suggested before, Carlos, you could temporarily move one of the servers to your quadcore (or any other connected machine, for that matter) during the rally--that would fix the problem.

[quote=Anonymous;126707]I think non-server versions of Windows have their own limit on connections--so yeah, I guess the only thing we can do about that is offload one or more of the LLRnet servers onto another machine. Or you could always put Linux on the LLRnet server, I don't think it has that limit.

Gary, did you read my LLRnet tutorials I sent you yet?[/quote]

Not going to have time this afternoon. I've been too long at this. Need to spend some time with kiddies that I only every Wed. and every other weekend.

Don't worry. I'll check it out Sunday.