PRPnet 2nd drive-51 bases with <= 5 k's to n=250K - Page 14

rogue · 2013-07-25, 12:46

I hope that this server get upgraded to PRPNet 5.x when a new project starts up on it.

mdettweiler · 2013-07-26, 23:11

Quote:

Originally Posted by rogue

I hope that this server get upgraded to PRPNet 5.x when a new project starts up on it.

Ah, you read my mind...just before I came over to check this subforum I was reading the PRPnet 5.x thread in Software to catch up on what an upgrade would entail.

Currently, we have three public servers that need to be upgraded: NPLB 9000 running v4.1.4; NPLB 2000 running v4.3.6; and CRUS 1400 running v4.3.6. We have a number of users who are still running 4.2.x or 4.1.x clients (all or most of Gary's, and some of mine; Ian may have some older clients floating around as well); so, I'm thinking we'll need to do this in two steps, first to 5.1.0 as a bridge since it's fully compatible with all 4.x and 5.x clients; and then to 5.2.6 after we've given everyone a few weeks to upgrade their clients.

This brings up another question, for everyone here: would people prefer to "carry over" the stats from the current port 1400 effort into the new one on the server, or start fresh for the new drive? I can take a backup of the stats from this drive before resetting and post it as a static web page on the CRUS site.

rogue · 2013-07-27, 01:17

I suggest you take these steps:

1) Migrate servers from 4.1.x to 4.3.x immediately. All you have to do is create the table CandidateGFNDivisor.
2) Get users to migrate their clients to 5.2.x.
3) Migrate servers from 4.3.x to 5.2.x.

Step 1 must be done first because in the 5.2.x server dropped support for clients older than 4.3.

Step 2 will take the most time because users might need to update multiple clients. The prpclient.ini file has a number of changes from 4.1.x to 5.2.x. It is best for users to start with a new one and modify as needed.

For step 3 you will have to decide if anyone with really old clients (pre 4.3) should be left high and dry. Since you have e-mail addresses, it shouldn't be hard to contact those people and let them know what they to do to upgrade.

The 4.3.x server is backward compatible with 4.1.x clients. The 5.2.x clients are backwards compatible with 4.3.x servers. Migrating the servers from 4.3.x to 5.2.x requires a couple more steps, i.e. first adding tables for 5.0.x (which isn't really necessary), then modifying for 5.2.x.

if you fear problems with the server migration, you can take a backup of the database before migrating. You can also copy the database then upgrade and do some testing just to make sure, but I've been fairly good at specifying compatibility issues between versions, so I'm not worried.

The biggest server improvements in 4.3.x over 4.1.x is more stats pages, such as pending_tests.html, lower memory usage, and numerous bug fixes.

The biggest server improvements in 5.2.x over 4.3.x are better stats pages (with links to each from each page), sorting of stats, and more bug fixes (of course).

mdettweiler · 2013-07-27, 05:49

Okay, so I just logged into the NPLB server box to check something (misspelled port 1400 greeting, which turned out to be correct when I actually opened the file...odd), and I noticed that Gary is actually using 4.3.1 for all his clients. Now that I think about it, I remember making an upgrade package for him to go from 4.0.6 to 4.3.1. So, anyway, it looks like all his clients are indeed new enough that they shouldn't be affected by a server upgrade. I'll see about making him an update package soon for 5.2.x.

Is there anyone else here still running antique 4.2 clients, or just me?

If so, we're golden, since it's just a dualcore that I have physical access to at present.

henryzz · 2013-07-27, 11:17

Looks like I will need to use my v5 clients on 9000 rather than 3.2 in future.

mdettweiler · 2013-07-29, 20:11

Quote:

Originally Posted by henryzz

Looks like I will need to use my v5 clients on 9000 rather than 3.2 in future.

Can you upgrade the 3.2 clients to a newer version, or is that not an option?

rogue · 2013-07-29, 22:24

I found a bug in the 5.2.6 server that causes it to crash. 5.2.5 will work though as I introduced the bug in 5.2.6. I will post an update later tonight.

henryzz · 2013-08-01, 14:47

Quote:

Originally Posted by mdettweiler

Can you upgrade the 3.2 clients to a newer version, or is that not an option?

I am on 5.0.8 for my personal sever and the clients that feed it. I just never added nplb to that INI file. I might even upgrade to the latest while I am at it.

rogue · 2013-08-01, 15:07

I added a bug in the 5.2.6 server. The fix is simple. I just haven't gotten around to posting it yet.

MyDogBuster · 2013-08-03, 08:41

Looks like Port 1400 will run out shortly. Since no one objected, I say we do R6/S6 - R16/S16 and the base 2 stuff.

I know there was talk of upgading the server, but with Gary out of town, that might be a problem. Maybe we could just load the new stuff into the old server and upgrade when Gary gets home.

BTW, great job on the completed stuff. That was a lot of work.

rogue · 2013-08-03, 13:36

Quote:

Originally Posted by MyDogBuster

Looks like Port 1400 will run out shortly. Since no one objected, I say we do R6/S6 - R16/S16 and the base 2 stuff.

I know there was talk of upgading the server, but with Gary out of town, that might be a problem. Maybe we could just load the new stuff into the old server and upgrade when Gary gets home.

I think we're better off letting Gary choose the course of action. Although upgrading from 4.3.x to 5.2.x isn't hard, he tends to be very cautious.

2013-07-29, 22:24	#150
rogue "Mark" Apr 2003 Between here and the 2⁴×397 Posts	I found a bug in the 5.2.6 server that causes it to crash. 5.2.5 will work though as I introduced the bug in 5.2.6. I will post an update later tonight. Last fiddled with by rogue on 2013-07-29 at 22:24

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Other Bases?	wblipp	GPU Computing	50	2012-10-11 13:23
New PRPnet drive discussion	mdettweiler	Conjectures 'R Us	89	2011-08-10 09:01
PRPnet 1st drive-R/S base 2 even-k/even-n/odd-n	mdettweiler	Conjectures 'R Us	153	2011-08-10 06:54
Subproject #1: 210k-250k sequences to 100 digits	henryzz	Aliquot Sequences	204	2009-07-30 12:06
Different bases = different times?	roger	Information & Answers	1	2007-04-25 14:35

2013-07-25, 12:46	#144
rogue "Mark" Apr 2003 Between here and the 1100011010000₂ Posts	I hope that this server get upgraded to PRPNet 5.x when a new project starts up on it.

2013-07-27, 01:17	#146
rogue "Mark" Apr 2003 Between here and the 2⁴×397 Posts	I suggest you take these steps: 1) Migrate servers from 4.1.x to 4.3.x immediately. All you have to do is create the table CandidateGFNDivisor. 2) Get users to migrate their clients to 5.2.x. 3) Migrate servers from 4.3.x to 5.2.x. Step 1 must be done first because in the 5.2.x server dropped support for clients older than 4.3. Step 2 will take the most time because users might need to update multiple clients. The prpclient.ini file has a number of changes from 4.1.x to 5.2.x. It is best for users to start with a new one and modify as needed. For step 3 you will have to decide if anyone with really old clients (pre 4.3) should be left high and dry. Since you have e-mail addresses, it shouldn't be hard to contact those people and let them know what they to do to upgrade. The 4.3.x server is backward compatible with 4.1.x clients. The 5.2.x clients are backwards compatible with 4.3.x servers. Migrating the servers from 4.3.x to 5.2.x requires a couple more steps, i.e. first adding tables for 5.0.x (which isn't really necessary), then modifying for 5.2.x. if you fear problems with the server migration, you can take a backup of the database before migrating. You can also copy the database then upgrade and do some testing just to make sure, but I've been fairly good at specifying compatibility issues between versions, so I'm not worried. The biggest server improvements in 4.3.x over 4.1.x is more stats pages, such as pending_tests.html, lower memory usage, and numerous bug fixes. The biggest server improvements in 5.2.x over 4.3.x are better stats pages (with links to each from each page), sorting of stats, and more bug fixes (of course).

2013-07-27, 05:49	#147
mdettweiler A Sunny Moo Aug 2007 USA (GMT-5) 14151₈ Posts	Okay, so I just logged into the NPLB server box to check something (misspelled port 1400 greeting, which turned out to be correct when I actually opened the file...odd), and I noticed that Gary is actually using 4.3.1 for all his clients. Now that I think about it, I remember making an upgrade package for him to go from 4.0.6 to 4.3.1. So, anyway, it looks like all his clients are indeed new enough that they shouldn't be affected by a server upgrade. I'll see about making him an update package soon for 5.2.x. Is there anyone else here still running antique 4.2 clients, or just me? If so, we're golden, since it's just a dualcore that I have physical access to at present.

2013-07-27, 11:17	#148
henryzz Just call me Henry "David" Sep 2007 Cambridge (GMT/BST) 1011011111001₂ Posts	Looks like I will need to use my v5 clients on 9000 rather than 3.2 in future.

2013-08-01, 15:07	#152
rogue "Mark" Apr 2003 Between here and the 2⁴×397 Posts	I added a bug in the 5.2.6 server. The fix is simple. I just haven't gotten around to posting it yet.

2013-08-03, 08:41	#153
MyDogBuster May 2008 Wilmington, DE 2²·23·31 Posts	Looks like Port 1400 will run out shortly. Since no one objected, I say we do R6/S6 - R16/S16 and the base 2 stuff. I know there was talk of upgading the server, but with Gary out of town, that might be a problem. Maybe we could just load the new stuff into the old server and upgrade when Gary gets home. BTW, great job on the completed stuff. That was a lot of work.