Upgraded to 2.1.0 and app is stuck on Starting Local Machine.
Already went into Virtual Box, removed the app, restarted Local. No change.
In VirtualBox, machine is powered off. Trying to start manually throws the error in the screenshot.
Error log is attached.
local-by-flywheel.log (2.5 KB)
Hi Clayton,
Sorry for the trouble!
Can you explain what all you did in VirtualBox? Did you attempt to delete the local-by-flywheel VM? I’m not suggesting you do it, I’m only asking for now.
Also, have you tried rebooting your computer like it suggests?
On another post you suggested to REMOVE the app from VB then restart Local. I did that as well as reboot my entire machine. Still not luck. I haven’t deleted the Local instance in VB as I guessed that would wipe out my databases. I hope REMOVE didn’t hurt it either.
Now when I start up Local, I get erros you can see in my log and then looking in VB, the Local instance is “powered off” without the ability to start manually. That is when I get the errors from the screenshot.
It seems like something may have gone awry when VirtualBox updated itself.
Can you please try downloading this VirtualBox installer and running it? http://download.virtualbox.org/virtualbox/5.1.30/VirtualBox-5.1.30-118389-Win.exe
That helped a bit. I installed VB again, restarted my computer, then started up Local and restarted Local. It is now hanging at Local Image Upgrade at about 30% for the past few minutes. The progress spinner on the right is just a gray dot. Here is what the erro log says
Nov 1, 2017, 3:43 PM CDT - info: [main/docker-machine] Machine "local-by-flywheel" was started.
Nov 1, 2017, 3:43 PM CDT - info: [main/docker-machine] Waiting for SSH to be available...
Nov 1, 2017, 3:43 PM CDT - info: [main/docker-machine] Detecting the provisioner...
Nov 1, 2017, 3:43 PM CDT - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Nov 1, 2017, 3:43 PM CDT - info: [main/set-docker-env] Getting Docker Machine env.
Nov 1, 2017, 3:43 PM CDT - info: [main/set-docker-env] Received Docker Machine env. export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://192.168.92.100:2376"
export DOCKER_CERT_PATH="C:\Users\Clayton\.docker\machine\machines\local-by-flywheel"
export DOCKER_MACHINE_NAME="local-by-flywheel"
export COMPOSE_CONVERT_WINDOWS_PATHS="true"
# Run this command to configure your shell:
# eval $("C:\Users\Clayton\AppData\Local\Programs\local-by-flywheel\resources\extraResources\virtual-machine\vendor\docker\windows\docker-machine.exe" env --shell bash local-by-flywheel)
Glad to hear!
Can you please provide the entire local-by-flywheel.log file again?
local-by-flywheel.log (14.2 KB)
Thanks!
Can you try closing Local and then re-opening it?
Great. I am now inside the app. I am getting these errors for all installs. My Local Sites folder is still in tact and in the same place as before.
That’s from deleting the VirtualBox VM. Sadly, “Remove” is synonymous with “Delete” in VirtualBox. I apologize for there not being a warning in my particular reply wherever you found the instructions.
I’m very sorry, but you’re going to need to reimport the sites to recreate the site containers. Here’s the current recommended way of going about this: How can I restore a site from a Local site folder?
We are going to be making it easier to restore sites from existing Local site folders in an upcoming version. I know that doesn’t help much now, but if some of the sites are on the backburner, you can hold off on recreating the site container for now.
Yeah that sucks the big one. Olny a couple of those are in active development.
I am trying to follow your article but am getting an error. Can you help troubleshoot that? I went to my Local Sites folder, renamed the 3817gilbert folder to 3817gilbert-backup, restarted Local, and went to Create new install. That is where I get the error. Do I need to delete the entire install from within Local to free up that name?
Yeah, after you rename the site folder you can delete the errored out site from Local.
Once again, I apologize! I’m going to talk to the team about making the restore process a priority in the coming development cycles.
Hey it’s totally OK. I did it to myself. I still love Local and really appreciate this level of support in a forum. At least the sql files are sitting right there.
