My SQL upgrade

*daniel77* · 02-14-2021, 12:13 PM

On another thread, back in July of 2020, Kevin indicated that the hurdle of upgrading to php 7.0 and SQL of 5.6 was being worked on. Has that been accomplished? Do we have to update my SQL or is that done automatically?

*Syneryder* · 02-15-2021, 06:22 AM

Quote:

Originally Posted by daniel77

On another thread, back in July of 2020, Kevin indicated that the hurdle of upgrading to php 7.0...

I assume that's a typo and you were actually talking about PHP 7.4, but just in case it isn't - you can change/update the PHP version in your CNC panel for your site. Once you're logged in, click on the Server Info link in the left, scroll down to the Version Information section, and at the bottom of that section you should see a blue Change PHP Version button. Click that and you'll have the option to switch your site to run PHP 7.3.14.

I don't see anything similar for MySQL though.

**Kevin** · 02-15-2021, 03:58 PM

We are down to 22 accounts that will require us to threaten loss of access to data unless the site owner does the prep work that needs to be done before a final deadline. This is mostly because I spent about 2 weeks trying to figuring out how to prep the other several hundred who had ignored our warnings. If you are curious, all you need to do is go into your CNC MySQL Manager. If it tells you that you must change your password that is the prep-work and you can even just change it to the existing password.

When we get ready to start the process the first step will be to evacuate and retire the 4 remaining 32-bit MySQL servers. This isn't technically needed but frankly I am done maintaining 2 separate OS cores just to keep these ancient servers going (there were 10 of them the last time we made a major change). This sounds like a big deal but it isn't really. No new accounts have been added to these servers in more than a decade and accounts sometimes leave so 1 semi-modern server would be able to take over the accounts from all 4. It would just be a time consuming process with about 10 minutes of downtime per account.

Then, (at least somewhat in parallel) we would need to make the new OS core with MySQL 5.6.x on a new server. The upgrade process would then be something like: move all the databases to the new server, start it upgrading the databases, (somewhat in parallel) install the new OS core on the old server, then finally move the upgraded databases to the previous server. I would probably do some benchmarking before the announcement to get better numbers but the downtime would probably be around 1-2 hours per server depending on the size of the server. Some of the older servers are running on 100Mbit instead of gigabit ethernet and we would probably do a 10-15 minute downtime for those servers prior to the upgrade to speed up the moving of the databases (also, network cards aren't all that expensive).

The good news is that these major hurdles only apply to 5.5.x > 5.6.x. There are some minor complications in going to 5.7.x but then going to 7.0.x and 8.0.x should be pretty smooth on our end. Each upgrade has compatibility issues that site owners who use in-house software would have to deal with. So, the current thinking is that once we get to 5.6.x we can do the other upgrades one per month. This would mostly depend on how open such site owners are to this.

*daniel77* · 02-15-2021, 07:22 PM

Thanks for the reply Kevin. Is there an ETA on getting this done? And I'm assuming most of this would be done at night so the downtime was minimally intrusive?

**Kevin** · 02-15-2021, 07:36 PM

Much of the downtime would be at night. Probably right after the backups. But we aren't ready to say when.

*Javier Mosqueda* · 02-16-2021, 02:16 AM

Hi Kevin I went to CNC DB mgr and did not see a warning in red or so, about changing password , though I've been away for long time and after reading the button "change password" it makes me wonder whether it's a suggestion to change it or that is the typical title of that button.

Greetings

**Kevin** · 02-16-2021, 02:31 AM

No, the warning is a popup and I don't think the CNC will let you do anything else in MySQL Manager until you do it.

**Kevin** · 02-16-2021, 02:42 AM

OK, I realized that it had been a long time since I saw it too (we started pushing this when we upgraded to 5.4.x) so I forced a password to the old format and tried it. I was right that it is a popup and I was right that you can't do anything else until you change your password to the new format. But I also discovered a bug (which we probably won't bother to fix for 22 users who will only ever see it once). If you close the popup window without hitting its "Change Password" button the you can't do anything else in MySQL Manager applies to the normal "Change Password" button. So, if you close the popup you have to reload the page to get it back.

*Javier Mosqueda* · 02-16-2021, 03:50 AM

Thanks Kevin!

*MarkW* · 02-08-2022, 05:48 PM

What are the issues that are preventing an upgrade to 8.x.x or MariaDB?

Version 8 is more than 3 year mature and the current version in production is more than 3 years beyond End of Support.