Local WP v. 9.2.9 still unable to start sites using MySQL 8.0.16

What issue or error are you experiencing?

This bug was added in Local v. 9.2.5 as I first reported in this topic: LocalWP v. 9.2.5 critical error on starting most sites

Here is the similar message from the current version of Local WP. To also answer the question from @nickc that I missed at the time - I am still seeing ‘mysql-8.0.16+6’ in the error message, and not ‘mysql-8.0.16+8’.

Questions

  1. Is there any plan to fix this bug in future releases of LocalWP?
  2. If not, is it possible possible to modify the configuration of my old LocalWP sites and manually change the MySQL version from 8.0.16 to 8.0.35 (this works without any problems)?

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

  • LocalWP v. >= 9.2.5
  • start a previous server created with the DB system MySQL 8.0.16

System Details

  • Local Version: Version 9.2.9+6887

  • Operating System (OS) and OS version:
    OS Name Ubuntu 22.04.5 LTS
    OS Type 64-bit
    GNOME Version 42.9
    Windowing System Wayland


Local Logs

The relevant portion of the log:

local-lightning.log (3.8 KB)

I looked on my own to find a solution for updating the mysql version and I found mostly the hard way: export the current site, then reimport it into a new site. With more than a dozen sites in this situation, that was not a practical solution for me.

Then I found this article that offered the solution: Local WP MySQL connection fix (after update) - Koen’s Blog

In my case, I had to update the file ~/.config/Local/sites.json

I followed this procedure:

  • I closed LocalWP
  • I identified the sites.json file
  • I copied the file for backup purposes
  • I edited the file with a text editor and replaced the version for one site from 8.0.16 to 8.0.35 then saved and closed the file
  • I opened LocalWP and tested the modified site => it displayed the updated version in LocalWP and started + worked normally
  • I closed LocalWP
  • I reopened the sites.json file and did a search and replace looking for “name”:“mysql”,“version”:“8.0.16” and replacing with “name”:“mysql”,“version”:“8.0.35”, then saved and closed the file
  • I tested several sites that were configured to use MySQL 8.0.16 before and they worked fine.

It seems that this procedure solved the problem for me. Still, I remain available for testing the initial error, if needed.

1 Like

Thank you for following up here with what resolved this for you @mihaipmp! Others might find that useful as well. We will continue to investigate this and let you know if we need any further help or have any follow up questions :smiling_face_with_sunglasses:

1 Like

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.