24 hour rally - Page 8

em99010pepe · 2008-02-09, 20:31

Increase your cache wu to 10...I'm receiving work from UK, USA, Germany, Italy...

gd_barnes · 2008-02-09, 20:39

I'll try that but I don't think the WU cache will make any difference. The machines have cleaned out their work units and can't seem to receive any more. Now my kid's Athlon is down to its final k/n pair on each core with no more being fed to it. I'll see it will load up another 5.

My Dell CD has 25 queued units, which is something I tried last night. It has remained consistenly full the whole time here.

em99010pepe · 2008-02-09, 20:42

Quote:

Originally Posted by gd_barnes

I'll try that but I don't think the WU cache will make any difference. The machines have cleaned out their work units and can't seem to receive any more. Now my kid's Athlon is down to its final k/n pair on each core with no more being fed to it. I'll see it will load up another 5.

My Dell CD has 25 queued units, which is something I tried last night. It has remained consistenly full the whole time here.

Athlon are not good for LLRing but don't forget to stop the client before editing the client configuration file. Do you want me to be mean? Next time test all your machines not on the rally day...lol

gd_barnes · 2008-02-09, 20:46

Agreed. I tested my Athlon and DC duo last night...no problems. My Athlon has had the most problems today. My kid's Athlon is the exact same machine purchased at the same time.

Now my kid's Athlon is sleeping. No longer receiving work. It completed 6 tests on each core and none of them have been sent to the server. This drops me to 2 cores after initially having 5 running.

I'm going to try one more thing.

gd_barnes · 2008-02-09, 21:09

I tried changing the port back to 6999 on each of the machines first core. No luck. I tried dropping the firewall completely. No luck. Still 'sleeping' or 'connecting' forever. Even when they connect, they end up 'sleeping'. There is some reason that the sever won't feed them work, even with a firewall completely dropped, i.e. allowing all possible programs.

But now my P4 is recieving work again so back to 3 cores; fortunately the fastest LLRing ones. The Athlon's are hopeless...back to sieving on them.

Gary

ET_ · 2008-02-09, 21:20

Quote:

Originally Posted by gd_barnes

I tried changing the port back to 6999 on each of the machines first core. No luck. I tried dropping the firewall completely. No luck. Still 'sleeping' or 'connecting' forever. Even when they connect, they end up 'sleeping'. There is some reason that the sever won't feed them work, even with a firewall completely dropped, i.e. allowing all possible programs.

But now my P4 is recieving work again so back to 3 cores; fortunately the fastest LLRing ones. The Athlon's are hopeless...back to sieving on them.

Gary

I'm having troubles with my mobile AMD64.
Big troubles with Windows firewall and the wireless suddenly shhut up.

NEXT TIME i'LL CHOOSE lINUX.

Luigi

gd_barnes · 2008-02-09, 21:26

OK, guys. We've got lift off! After losing 2+ hours, all 7 cores are running LLRnet.

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

em99010pepe · 2008-02-09, 22:55

This message is only for the ones who increased their cache wu's to more than 30. I only ask, in case they are going to abandon NPLB project after the rally, to set up the cache to 1 and to process what they have left on the cache. After only reaching one wu, stop the client and edit the client config file and take the two dashes as showed bellow on the following command:

Code:

-- uncomment line below to work only once
once = 1

This will tell the client to process its last unit cache and to close off the client.

At this post the server is distributing numbers above 328.4K...hehe..still more than 50 000 k/n pairs in the server.

BlisteringSheep · 2008-02-09, 22:58

Had a couple hours of downtime - the IP address of crus.dynip.telepac.pt changed, and since it's running on port 300 (in the privileged range), I had to restart my firewall.

Also added my 1 GHz Athlon.

em99010pepe · 2008-02-09, 22:59

Quote:

Originally Posted by BlisteringSheep

Had a couple hours of downtime - the IP address of crus.dynip.telepac.pt changed, and since it's running on port 300 (in the privileged range), I had to restart my firewall.

Also added my 1 GHz Athlon.

It's a dynamic IP and it changed 15 min after the start of the rally, sorry, I can't control that.

BlisteringSheep · 2008-02-09, 23:01

Quote:

Originally Posted by em99010pepe

This message is only for the ones who increased their cache wu's to more than 30. I only ask, in case they are going to abandon NPLB project after the rally, to set up the cache to 1 and to process what they have left on the cache. After only reaching one wu, stop the client and edit the client config file and take the two dashes as showed bellow on the following command:

Code:

-- uncomment line below to work only once
once = 1

This will tell the client to process its last unit cache and to close off the client.

At this post the server is distributing numbers above 328.4K...hehe..still more than 50 000 k/n pairs in the server.

I will continue these four machines at least through tomorrow. I did bump my caches up in the interim, but won't abandon any work.

When I get my new dual E5440 2.83ghz put together (hope to have all of the parts by next weekend), I may put some of it on NPLB.

2008-02-09, 20:31	#78
em99010pepe Sep 2004 2×5×283 Posts	Increase your cache wu to 10...I'm receiving work from UK, USA, Germany, Italy... Last fiddled with by em99010pepe on 2008-02-09 at 20:31

2008-02-09, 22:55	#85
em99010pepe Sep 2004 2×5×283 Posts	This message is only for the ones who increased their cache wu's to more than 30. I only ask, in case they are going to abandon NPLB project after the rally, to set up the cache to 1 and to process what they have left on the cache. After only reaching one wu, stop the client and edit the client config file and take the two dashes as showed bellow on the following command: Code: -- uncomment line below to work only once once = 1 This will tell the client to process its last unit cache and to close off the client. At this post the server is distributing numbers above 328.4K...hehe..still more than 50 000 k/n pairs in the server. Last fiddled with by em99010pepe on 2008-02-09 at 22:58

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
24 hour news	davieddy	Soap Box	4	2011-12-19 19:35
mfaktc slows on WinXP after about an hour	Christenson	GPU Computing	5	2011-05-27 21:47
Prime 95 shuts down itself after exactly 9:22 hour	Unregistered	Information & Answers	13	2009-09-02 05:11
! hour limit on editing	davieddy	Lounge	7	2009-09-01 15:57
1 buck an hour	crash893	Hardware	6	2009-06-18 01:45

2008-02-09, 20:39	#79
gd_barnes May 2007 Kansas; USA 3³×5×7×11 Posts	I'll try that but I don't think the WU cache will make any difference. The machines have cleaned out their work units and can't seem to receive any more. Now my kid's Athlon is down to its final k/n pair on each core with no more being fed to it. I'll see it will load up another 5. My Dell CD has 25 queued units, which is something I tried last night. It has remained consistenly full the whole time here.

2008-02-09, 20:46	#81
gd_barnes May 2007 Kansas; USA 3³·5·7·11 Posts	Agreed. I tested my Athlon and DC duo last night...no problems. My Athlon has had the most problems today. My kid's Athlon is the exact same machine purchased at the same time. Now my kid's Athlon is sleeping. No longer receiving work. It completed 6 tests on each core and none of them have been sent to the server. This drops me to 2 cores after initially having 5 running. I'm going to try one more thing.

2008-02-09, 21:09	#82
gd_barnes May 2007 Kansas; USA 3³×5×7×11 Posts	I tried changing the port back to 6999 on each of the machines first core. No luck. I tried dropping the firewall completely. No luck. Still 'sleeping' or 'connecting' forever. Even when they connect, they end up 'sleeping'. There is some reason that the sever won't feed them work, even with a firewall completely dropped, i.e. allowing all possible programs. But now my P4 is recieving work again so back to 3 cores; fortunately the fastest LLRing ones. The Athlon's are hopeless...back to sieving on them. Gary

2008-02-09, 21:26	#84
gd_barnes May 2007 Kansas; USA 3³×5×7×11 Posts	OK, guys. We've got lift off! After losing 2+ hours, all 7 cores are running LLRnet. 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

2008-02-09, 22:58	#86
BlisteringSheep Oct 2006 On a Suzuki Boulevard C90 246₁₀ Posts	Had a couple hours of downtime - the IP address of crus.dynip.telepac.pt changed, and since it's running on port 300 (in the privileged range), I had to restart my firewall. Also added my 1 GHz Athlon.