I’ve had a long history of wrestling with local development environments. While I haven’t written much (none) about it, for the last year plus I’ve relied on Local by Flywheel to develop WordPress websites. The main reason: It’s been easy to use, and most importantly, super duper reliable. It’s also fast.
Until recently that is. Periodically the app would get stuck when adding a new site. No errors reported it would just continually stay on provisioning – installing WordPress.
Flywheel to the rescue
A web search on the issue turned up a whole lot of not much. So while I didn’t expect much, I turned to the Flywheel forum and posted a support request (After searching there first, of course). To my surprise, Clay Griffiths responded in a couple of minutes. After a bit of back and forth, he reviewed my log file and found the issue:
May 22, 2018, 5:07 PM MDT - info: [worker: mysql-worker] /etc/init.d/mysql: ERROR: The partition with /var/lib/mysql is too full! ...
So the issue is that the VM disk space in VirtualBox was full. Here’s the options he offered up to fix. I chose Option B:
Option A:
See Unable to connect to database on any site previously working working without issue
Option B:
- Export all of your Local sites by starting them in Local and then right-clicking on them and going to “Export”
- Verify that there is an exported archive for all of the sites
- Quit Local
- Open VirtualBox
- Right-click on
local-by-flywheel - Go to Close » Power Off
- Right-click again and go to Remove and then delete all files
- Re-open Local and go through the installation process
- Click into the sites in Local and click on the “Restore” button when prompted
- Test adding a new site
Thanks Clay and Flywheel for the great support. My issue is resolved and it seems like Local is running faster than ever.
- List 1
- List 2
- List 3