LLRnet servers for NPLB - Page 96

gd_barnes · 2009-06-09, 17:18

BIG storm here right now. Expect a power blip at any point.

I have to head out for 30 mins. right now.

...put the battery back in my laptop for the time being.

Max, if you can show me how to run the loop thingie if it's not too technical, I'll do that. Otherwise if it goes down, I restart it, and then it crashes with the 1st prune, I'll temporarily change the prune period to 86400 secs. again.

mdettweiler · 2009-06-09, 18:50

Quote:

Originally Posted by gd_barnes

BIG storm here right now. Expect a power blip at any point.

I have to head out for 30 mins. right now.

...put the battery back in my laptop for the time being.

Max, if you can show me how to run the loop thingie if it's not too technical, I'll do that. Otherwise if it goes down, I restart it, and then it crashes with the 1st prune, I'll temporarily change the prune period to 86400 secs. again.

Okay, for the loop thingy, instead of running the command ./llrnet llrserver.lua for each one, run this string of commands (all on one line, then press Enter at the end):

while ./llrnet llrserver.lua ; do echo "Restarting server! *******************" >> restart.log ; done

Note that with this in place, if you need to stop the server with Ctrl-C, it will just immediately restart. Thus, you'd need to terminate the loop itself in order to kill the server. This can be done by closing out the terminal tab the server resides in, or by killing the while loop directly. (Probably closing out the tab is the easiest.)

Max

P.S.: I'll see about doing some research on UPS units. If we could get your computers on one of them that would be a huge godsend.

gd_barnes · 2009-06-22, 12:49

Port 2000 will be processing our 11th drive. I have now added it to the 1st post of this thread. David is already aware that we will be using that port for the drive.

Max, Ian, or Karsten, can you take care of getting the Email notification turned on for primes on that port? It was previously used for double-checking so I doubt the notification is turned on at the moment.

Gary

MyDogBuster · 2009-06-22, 13:27

Quote:

Max, Ian, or Karsten, can you take care of getting the Email notification turned on for primes on that port? It was previously used for double-checking so I doubt the notification is turned on at the moment.

Done

gd_barnes · 2009-06-23, 02:31

Can someone with an LLRnet server ID of "llrserver" please identify yourself?

If someone caches 100's of pairs at once without returning any to the server over 10 hours, we need to know who is doing this to prevent potential monkey business.

David, if we don't get a response to this post by Tues. morning U.S., I will suggest that you temporarily change the JobMaxTime from 3 days to 12 hours so that the pairs get quickly handed back out to others. If the problem continues, we may drop it all the way to 3 hours for a while. ...Sorry regular folks; this looks very suspicious.

Gary

gd_barnes · 2009-06-23, 07:46

David,

Please change the JobMaxTime on port 2000 to 12 hours to clear out pairs taken in an unusual manner by 'llrserver'.

For our regulars, for the time being, please make sure you don't cache more than you can complete in 12 hours. AFAIK, it's just Karsten and me on the server right now and nothing (except for the llrserver ID) has been taking any longer than about 20 minutes; which is me cacheing 5 pairs at a time.

When we change it back, we may just go to 24 hours instead of 3 days, especially at these lower n-ranges.

One more thing: Is there a way to prevent people from cacheing more than 100 or 200 pairs at a time? I'm asking because we're quite vulnerable to having a large quantity of pairs "swiped" by just about anyone for their own nefarious means. Even for non-connected people who wish to return a large quantity at once on a different connected machine, I can't see a reason to ever cache more 200 pairs at once.

Thanks,
Gary

AMDave · 2009-06-23, 10:05

investigating

AMDave · 2009-06-23, 11:15

settings changed to 12 hour jobMax
service re-started (diff mode - I will PM admins)

MyDogBuster · 2009-06-24, 03:22

Something amiss on IB2000. According to results file, nothing has returned in the last 5 hours. Slackards. LOL

gd_barnes · 2009-06-24, 03:34

Damn. Checking my machines now. They may not have reconnected after the outage.

gd_barnes · 2009-06-24, 03:58

No, my machines are good and ready to connect to the server. I killed the processes and tried restarting them...no luck.

Port 2000 is officially dead in the water at the moment. AMDave is apparently not available. I just sent Ironbits an Email.

2009-06-09, 17:18	#1046
gd_barnes May 2007 Kansas; USA 10311₁₀ Posts	BIG storm here right now. Expect a power blip at any point. I have to head out for 30 mins. right now. ...put the battery back in my laptop for the time being. Max, if you can show me how to run the loop thingie if it's not too technical, I'll do that. Otherwise if it goes down, I restart it, and then it crashes with the 1st prune, I'll temporarily change the prune period to 86400 secs. again. Last fiddled with by gd_barnes on 2009-06-09 at 17:20

2009-06-23, 11:15	#1053
AMDave Jan 2006 deep in a while-loop 2×7×47 Posts	settings changed to 12 hour jobMax service re-started (diff mode - I will PM admins) Last fiddled with by AMDave on 2009-06-23 at 11:16

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
PRPnet servers for NPLB	mdettweiler	No Prime Left Behind	228	2018-12-26 04:50
Servers for NPLB	gd_barnes	No Prime Left Behind	0	2009-08-10 19:21
LLRnet servers for CRUS	gd_barnes	Conjectures 'R Us	39	2008-07-15 10:26
NPLB LLRnet server discussion	em99010pepe	No Prime Left Behind	229	2008-04-30 19:13
NPLB LLRnet server #1 - dried	em99010pepe	No Prime Left Behind	19	2008-03-26 06:19

2009-06-22, 12:49	#1048
gd_barnes May 2007 Kansas; USA 3·7·491 Posts	Port 2000 will be processing our 11th drive. I have now added it to the 1st post of this thread. David is already aware that we will be using that port for the drive. Max, Ian, or Karsten, can you take care of getting the Email notification turned on for primes on that port? It was previously used for double-checking so I doubt the notification is turned on at the moment. Gary

2009-06-23, 02:31	#1050
gd_barnes May 2007 Kansas; USA 10311₁₀ Posts	Can someone with an LLRnet server ID of "llrserver" please identify yourself? If someone caches 100's of pairs at once without returning any to the server over 10 hours, we need to know who is doing this to prevent potential monkey business. David, if we don't get a response to this post by Tues. morning U.S., I will suggest that you temporarily change the JobMaxTime from 3 days to 12 hours so that the pairs get quickly handed back out to others. If the problem continues, we may drop it all the way to 3 hours for a while. ...Sorry regular folks; this looks very suspicious. Gary

2009-06-23, 07:46	#1051
gd_barnes May 2007 Kansas; USA 3·7·491 Posts	David, Please change the JobMaxTime on port 2000 to 12 hours to clear out pairs taken in an unusual manner by 'llrserver'. For our regulars, for the time being, please make sure you don't cache more than you can complete in 12 hours. AFAIK, it's just Karsten and me on the server right now and nothing (except for the llrserver ID) has been taking any longer than about 20 minutes; which is me cacheing 5 pairs at a time. When we change it back, we may just go to 24 hours instead of 3 days, especially at these lower n-ranges. One more thing: Is there a way to prevent people from cacheing more than 100 or 200 pairs at a time? I'm asking because we're quite vulnerable to having a large quantity of pairs "swiped" by just about anyone for their own nefarious means. Even for non-connected people who wish to return a large quantity at once on a different connected machine, I can't see a reason to ever cache more 200 pairs at once. Thanks, Gary

2009-06-23, 10:05	#1052
AMDave Jan 2006 deep in a while-loop 658₁₀ Posts	investigating

2009-06-24, 03:22	#1054
MyDogBuster May 2008 Wilmington, DE 101100100100₂ Posts	Something amiss on IB2000. According to results file, nothing has returned in the last 5 hours. Slackards. LOL

2009-06-24, 03:34	#1055
gd_barnes May 2007 Kansas; USA 3×7×491 Posts	Damn. Checking my machines now. They may not have reconnected after the outage.

2009-06-24, 03:58	#1056
gd_barnes May 2007 Kansas; USA 3×7×491 Posts	No, my machines are good and ready to connect to the server. I killed the processes and tried restarting them...no luck. Port 2000 is officially dead in the water at the moment. AMDave is apparently not available. I just sent Ironbits an Email.