Minutes between network retries - issue with 60

petrw1 · 2007-10-05, 17:49

One of my computers did NOT successfully check in results for almost a day (it is set for a daily check in). When I looked at the messages to determine why I noticed that every 60 minutes I was getting the "server busy" error. I noticed that it was trying every 60 minutes just after the hour. It occured to me that the primenet server updates some statistics, reports and web pages also every hour on the hour. This leads me to believe that is why the update is failing over and over. The server is too busy for the first few minutes after each hour to reliably respond to results updates.

To resolve my immediate issue I manually communicated the results at a non-busy time.

In the short term I plan to change my "minutes between network retries" to a number that is not 60 or a multiple of 60.

In the long term I would suggest that the primenet default for this parameter be set to something other than 60 as well so if it fails at 8:03 with a server busy message it won't try again and 9:03 and fail again, etc, etc.

Kevin · 2007-10-05, 18:37

Already fixed in the new version being beta tested, default value is set to 70.

2007-10-05, 17:49	#1
petrw1 1976 Toyota Corona years forever! "Wayne" Nov 2006 Saskatchewan, Canada 1001001000100₂ Posts	Minutes between network retries - issue with 60 One of my computers did NOT successfully check in results for almost a day (it is set for a daily check in). When I looked at the messages to determine why I noticed that every 60 minutes I was getting the "server busy" error. I noticed that it was trying every 60 minutes just after the hour. It occured to me that the primenet server updates some statistics, reports and web pages also every hour on the hour. This leads me to believe that is why the update is failing over and over. The server is too busy for the first few minutes after each hour to reliably respond to results updates. To resolve my immediate issue I manually communicated the results at a non-busy time. In the short term I plan to change my "minutes between network retries" to a number that is not 60 or a multiple of 60. In the long term I would suggest that the primenet default for this parameter be set to something other than 60 as well so if it fails at 8:03 with a server busy message it won't try again and 9:03 and fail again, etc, etc.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
The Expanse has to be the most epic 45 minutes to get a first showing on regular cable.	jasong	jasong	25	2016-01-21 16:03
factoring 90 512-bit RSA Keys in 3 minutes	Mini-Geek	Lounge	1	2015-03-17 17:27
Feature request - contacting server again in 67 minutes	patrik	Software	3	2006-09-25 06:37
Any puzzle I can't solve in 15 minutes is to be considered HARD	JuanTutors	Puzzles	14	2005-05-27 21:27
Primality test - 0,03% in 105 minutes. It is too much....	chrow	Software	4	2003-06-26 09:59

2007-10-05, 18:37	#2
Kevin Aug 2002 Ann Arbor, MI 433 Posts	Already fixed in the new version being beta tested, default value is set to 70.