"Starting Local Machine" hanging issue

Support
1

Hi there,

I’ve been working on a site and I believe everything was fine up until I restarted my Mac this afternoon. When I logged back in to continue work, Local is just hanging on the “Starting Local Machine” screen. I can see others with the issue but figured I can give you the key bits of the log file I’m seeing. Please help!

iMac 27" 5k, MacOS Sierra v10.12.3

---- Log -----

Mar 18, 2017, 7:36 PM GMT+13 - info: [main/index] Existing Pressmatic data does not exist.
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/check-system] Check System: Docker Machine:
{ stdout: ‘Stopped\n’, stderr: ‘’ }
Mar 18, 2017, 7:36 PM GMT+13 - info: [renderer/RendererAddonLoader] Renderer Loading Add-on: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/addons/local-addon-demo-urls/lib/renderer.js
Mar 18, 2017, 7:36 PM GMT+13 - info: [renderer/RendererAddonLoader] Renderer Successfully Loaded Add-on: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/addons/local-addon-demo-urls/lib/renderer.js
Mar 18, 2017, 7:36 PM GMT+13 - info: [renderer/RendererAddonLoader] Renderer Loading Add-on: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/addons/local-addon-intellij-xdebug/lib/renderer.js
Mar 18, 2017, 7:36 PM GMT+13 - info: [renderer/RendererAddonLoader] Renderer Successfully Loaded Add-on: /Applications/Local by Flywheel.app/Contents/Resources/extraResources/addons/local-addon-intellij-xdebug/lib/renderer.js
Mar 18, 2017, 7:36 PM GMT+13 - info: [renderer/CheckEnvPage] Check system promise response: [ undefined, ‘machine-halted’ ] machine-halted
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] Running /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] Starting “local-by-flywheel”…
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed…
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] (local-by-flywheel) Creating a new host-only adapter produced an error: /usr/local/bin/VBoxManage hostonlyif create failed:
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] (local-by-flywheel) 0%…
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] (local-by-flywheel) Progress state: NS_ERROR_FAILURE
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] (local-by-flywheel) VBoxManage: error: Failed to create the host-only adapter
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] (local-by-flywheel) VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: Permission denied
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] (local-by-flywheel) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] (local-by-flywheel) VBoxManage: error: Context: “RTEXITCODE handleCreate(HandlerArg *)” at line 71 of file VBoxManageHostonly.cpp
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] (local-by-flywheel)
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/docker-machine] (local-by-flywheel) This is a known VirtualBox bug. Let’s try to recover anyway…
Mar 18, 2017, 7:36 PM GMT+13 - info: [main/autoUpdater] Update for darwin-x64-production-v1.4.2 is not available
Mar 18, 2017, 7:36 PM GMT+13 - warn: [main/docker-machine] Error setting up host only network on machine start: The host-only adapter we just created is not visible. This is a well known VirtualBox bug. You might want to uninstall it and reinstall at least version 5.0.12 that is is supposed to fix this issue

Would love a fix, even if it involves getting hands dirty for now… :slight_smile:

1 Like
2

Hi Andy,

Did you figure out how to solve this? I’ve been trying to make it work for few hours. Finally, I went to Virtual Box and reset the local-by-flywheel as advised somewhere in this forum… Well, I get a flywheel starting now but with no install at all. Look like I lost few projects there :frowning:
So be careful playing with all the settings!

3

Hey all,

Very sorry for the trouble!

You can also try upgrading to the latest VirtualBox. You can download it here: https://www.virtualbox.org/wiki/Downloads

4

Updating Vagrant (which I manage through a brew cask) fixed this. However, the re-launch of Local after that update was unusually slow (2 minutes) so be patient. 2nd launch was instant like usual.

FYI, I’m now running OSX 10.12.4, Vagrant 1.9.2, Virtual Box 5.1.18, Local 1.4.2