mersenneforum.org Avoid ”Restarting all worker windows using new settings.“
 Register FAQ Search Today's Posts Mark Forums Read

 2020-10-20, 16:50 #1 Ensigm   Aug 2020 1628 Posts Avoid ”Restarting all worker windows using new settings.“ As noted in a previous thread, I'm doing some manual Pm1 factoring using mprime, and results are automatically reported to the server by using the following settings Code: NoMoreWork=1 ManualComm=0 UsePrimenet=1 in prime.txt. However, I notice sometimes the program will restart the worker shortly after it contacts the server, with the message ”Restarting all worker windows using new settings.“. If the restart happens during Stage 2, it will cause the loss of ~7 mins. I don't need to control the program settings from the mersenne.org. How to avoid this happening? Last fiddled with by Ensigm on 2020-10-20 at 16:51
 2020-10-20, 18:04 #2 Uncwilly 6809 > 6502     """"""""""""""""""" Aug 2003 101×103 Posts 23·1,171 Posts This is likely caused by time of day and your memory settings. It is likely only coincidental to the communication. What are your memory settings for day and night and the hours set for that. Look under "Options" the location has changed since v30 came out, so look around a little.
2020-10-20, 18:18   #3
Ensigm

Aug 2020

2×3×19 Posts

Quote:
 Originally Posted by Uncwilly This is likely caused by time of day and your memory settings. It is likely only coincidental to the communication. What are your memory settings for day and night and the hours set for that. Look under "Options" the location has changed since v30 came out, so look around a little.
My memory setting is
Code:
Memory=8192
in local.txt, with no difference between day and night.

I don't think it's coincidental. The terminal output I got in whole is
Code:
[Comm thread Oct 20 11:04] Updating computer information on the server
[Comm thread Oct 20 11:04] Exchanging program options with server
[Comm thread Oct 20 11:04] Exchanging program options with server
[Main thread Oct 20 11:04] Restarting all worker windows.
[Comm thread Oct 20 11:04] Done communicating with server.
[Work thread Oct 20 11:04] Worker stopped.
[Main thread Oct 20 11:04] Restarting all worker windows using new settings.
[Work thread Oct 20 11:04] Worker starting

Last fiddled with by Ensigm on 2020-10-20 at 18:20

 2020-12-05, 08:30 #4 pinhodecarlos     "Carlos Pinho" Oct 2011 Milton Keynes, UK 5×7×139 Posts Somehow now I can't manually communicate with the server, see picture below (p95v303b6.win64) Attached Thumbnails
2020-12-05, 08:37   #5
Ensigm

Aug 2020

2·3·19 Posts

Quote:
 Originally Posted by pinhodecarlos Somehow now I can't manually communicate with the server, see picture below (p95v303b6.win64)
I'm not using windows so I'm not sure about the problem, but maybe it has something to do with the ManualComm=0? I understand what the other two options do but not this one.

Last fiddled with by Ensigm on 2020-12-05 at 08:37

2020-12-05, 08:47   #6
pinhodecarlos

"Carlos Pinho"
Oct 2011
Milton Keynes, UK

5×7×139 Posts

Quote:
 Originally Posted by Ensigm I'm not using windows so I'm not sure about the problem, but maybe it has something to do with the ManualComm=0? I understand what the other two options do but not this one.
It doesn’t matter if I set to 0 or 1 or take it out.

 2020-12-05, 13:03 #7 kruoli     "Oliver" Sep 2017 Porta Westfalica, DE 22×109 Posts Have you set the tick of "Use PrimeNet to get work and report results" in Test/PrimeNet...?

 Similar Threads Thread Thread Starter Forum Replies Last Post drew PrimeNet 7 2020-01-06 15:51 storm5510 Software 10 2017-06-23 06:34 ixfd64 Software 0 2011-01-24 04:36 Unregistered Information & Answers 4 2010-07-30 21:49 markg Software 0 2008-08-04 13:52

All times are UTC. The time now is 09:14.

Thu Mar 4 09:14:36 UTC 2021 up 91 days, 5:25, 1 user, load averages: 1.77, 1.97, 1.91