Cannot start any sites

Support
1

I get the 'Missing hosts entry. This site may be inaccessible" warning - the ‘fix it’ button doesn’t do anything.

When I try and start - I get an error:

**Error when starting site** 
Error response from daemon: No such container: 4ab885727eb1177dbbb6c3b9922f342e212ddfdda35f611ce90d8728c8260636
Error: failed to start containers: 4ab885727eb1177dbbb6c3b9922f342e212ddfdda35f611ce90d8728c8260636

I can’t access database via Sequel Pro to export it either. Afraid to reinstall incase I lose my SQL files.

3

Very sorry for the trouble!

Did you attempt to delete this site at any time?

Also, can you please try going to Help » Restart Local’s Machine?

4

I didn’t try and delete, if anything just trying to get it to start so I can back up the database.

Local will start on this same machine under a different user but it’s just retrieving that database now which is the issue.

I tried to Restart Local’s Machine and got the following:

“Machine Unable to Restart”

There was an error when restarting the Local Machine. Please refer to the “local-by-flywheel.log” file.

Log file is this:

Jan 13, 2017, 4:56 PM GMT - info: [renderer/system-heartbeat] System Heartbeat: New timeoutID:  1
Jan 13, 2017, 4:56 PM GMT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine stop local-by-flywheel
Jan 13, 2017, 4:56 PM GMT - info: [renderer/system-heartbeat] System Heartbeat: Cleared timeoutID:  1
Jan 13, 2017, 4:56 PM GMT - info: [main/docker-machine] Stopping "local-by-flywheel"...
Jan 13, 2017, 4:56 PM GMT - warn: [main/docker-machine] Machine "local-by-flywheel" is already stopped.
Jan 13, 2017, 4:56 PM GMT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Jan 13, 2017, 4:56 PM GMT - info: [main/docker-machine] child process exited with code 1
Jan 13, 2017, 4:56 PM GMT - info: [main/docker-machine] Starting "local-by-flywheel"...
Jan 13, 2017, 4:56 PM GMT - info: [main/docker-machine] (local-by-flywheel) Check network to re-create if needed...
Jan 13, 2017, 4:56 PM GMT - warn: [main/docker-machine] Checking if hardware virtualization is enabled failed: open /Users/duanedoogan/.docker/machine/machines/local-by-flywheel/local-by-flywheel/Logs/VBox.log: no such file or directory
Jan 13, 2017, 4:56 PM GMT - info: [main/menu] Unable to restart Docker Machine.
Jan 13, 2017, 4:56 PM GMT - info: [renderer/CheckEnvPage] Check system promise response: [ undefined, 'machine-halted' ] machine-halted
Jan 13, 2017, 4:56 PM GMT - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start local-by-flywheel
Jan 13, 2017, 4:56 PM GMT - info: [main/docker-machine] Starting "local-by-flywheel"...
Jan 13, 2017, 4:56 PM GMT - warn: [main/docker-machine] Machine "local-by-flywheel" is already running.
Jan 13, 2017, 4:56 PM GMT - info: [main/set-docker-env] Getting Docker Machine env.
Jan 13, 2017, 4:57 PM GMT - warn: [main/set-docker-env] Error checking TLS connection: Something went wrong running an SSH command!
command : ip addr show
err     : exit status 255
output  : 


Jan 13, 2017, 4:57 PM GMT - info: [main/docker-machine] checking IP
Jan 13, 2017, 4:57 PM GMT - info: [main/set-docker-env] Getting Docker Machine env.
Jan 13, 2017, 4:57 PM GMT - info: [main/docker-machine] checked IP 
Jan 13, 2017, 4:57 PM GMT - warn: [main/set-docker-env] Error checking TLS connection: Something went wrong running an SSH command!
command : ip addr show
err     : exit status 255
output  : 


Jan 13, 2017, 4:57 PM GMT - info: [renderer/system-heartbeat] System Heartbeat: New timeoutID:  2
5

I am also having the same issue with two of the four projects I created with Pressmatic and now after being opened with Local by Flywheel no longer work in either app. Here’s an example of one of my errors:

Local_by_Flywheel.png848×424 54.7 KB

Here’s the Log files when trying to launch one broken site and then the other:

    Jan 31, 2017, 8:59 AM EST - info: [main/index] Existing Pressmatic data does not exist.
Jan 31, 2017, 8:59 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 8:59 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 8:59 AM EST - info: [main/set-docker-env] Getting Docker Machine env.
Jan 31, 2017, 8:59 AM EST - info: [renderer/RendererAddonLoader] Renderer Loading Add-on: /Users/petergray/Library/Application Support/Local by Flywheel/addons/pressmatic-addon-stats/lib/renderer.js
Jan 31, 2017, 8:59 AM EST - info: [renderer/RendererAddonLoader] Renderer Successfully Loaded Add-on: /Users/petergray/Library/Application Support/Local by Flywheel/addons/pressmatic-addon-stats/lib/renderer.js
Jan 31, 2017, 8:59 AM EST - warn: [renderer/RendererAddonLoader] Renderer Add-on not enabled: local-addon-demo-urls
Jan 31, 2017, 8:59 AM EST - warn: [renderer/RendererAddonLoader] Renderer Add-on not enabled: local-addon-intellij-xdebug
Jan 31, 2017, 8:59 AM EST - info: [renderer/CheckEnvPage] Check system promise response: 
{ '0': undefined, '1': undefined }
Jan 31, 2017, 8:59 AM EST - info: [renderer/system-heartbeat] System Heartbeat: New timeoutID:  4
Jan 31, 2017, 8:59 AM EST - info: [main/autoUpdater] Update for darwin-x64-production-v1.4.1 is not available
Jan 31, 2017, 9:00 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:00 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:00 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:00 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:00 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:00 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:00 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:00 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:00 AM EST - info: [main/verify-wp-cli] Verifying WP-CLI for c179e36ecf961333da20af8dd0af607e002b4519b974833937aa071c22d59a31.
Jan 31, 2017, 9:00 AM EST - info: [main/stopSite] Stopping site: running mydumper
Jan 31, 2017, 9:00 AM EST - info: [main/stopSite] Stopping site: running mydumper
Jan 31, 2017, 9:00 AM EST - info: [main/stopSite] Stopping site: running mydumper
Jan 31, 2017, 9:00 AM EST - info: [main/stopSite] Stopping site: killing container 2b707dbda88296469f3a9f6d6073e435367c9db621e2a045aa54932fc4b4a408
Jan 31, 2017, 9:00 AM EST - info: [main/stopSite] Stopping site: killing container 90854a82665d6226cd298f0dd565bb566104013fd4085523bab6e71ae7954529
Jan 31, 2017, 9:00 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:00 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:00 AM EST - info: [main/startSite] Running start 2b707dbda88296469f3a9f6d6073e435367c9db621e2a045aa54932fc4b4a408
Jan 31, 2017, 9:06 AM EST - info: [main/stopSite] Stopping site: killing container c179e36ecf961333da20af8dd0af607e002b4519b974833937aa071c22d59a31
Jan 31, 2017, 9:06 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:06 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:06 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:06 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:06 AM EST - info: [renderer/system-heartbeat] System Heartbeat: Cleared timeoutID:  4
Jan 31, 2017, 9:06 AM EST - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine stop pressmatic
Jan 31, 2017, 9:06 AM EST - info: [main/docker-machine] Stopping "pressmatic"...
Jan 31, 2017, 9:06 AM EST - info: [main/docker-machine] Machine "pressmatic" was stopped.
Jan 31, 2017, 9:06 AM EST - info: [main/docker-machine] Running  /Applications/Local by Flywheel.app/Contents/Resources/extraResources/virtual-machine/vendor/docker/osx/docker-machine start pressmatic
Jan 31, 2017, 9:06 AM EST - info: [main/docker-machine] child process exited with code 0
Jan 31, 2017, 9:06 AM EST - info: [main/docker-machine] Starting "pressmatic"...
Jan 31, 2017, 9:06 AM EST - info: [main/docker-machine] (pressmatic) Check network to re-create if needed...
Jan 31, 2017, 9:06 AM EST - info: [main/docker-machine] (pressmatic) Waiting for an IP...
Jan 31, 2017, 9:07 AM EST - info: [main/docker-machine] Machine "pressmatic" was started.
Jan 31, 2017, 9:07 AM EST - info: [main/docker-machine] Waiting for SSH to be available...
Jan 31, 2017, 9:07 AM EST - info: [main/docker-machine] Detecting the provisioner...
Jan 31, 2017, 9:07 AM EST - info: [main/docker-machine] Started machines may have new IP addresses. You may need to re-run the `docker-machine env` command.
Jan 31, 2017, 9:07 AM EST - info: [main/set-docker-env] Getting Docker Machine env.
Jan 31, 2017, 9:07 AM EST - info: [main/docker-machine] checking IP
Jan 31, 2017, 9:07 AM EST - info: [renderer/CheckEnvPage] Check system promise response: 
{ '0': undefined, '1': undefined }
Jan 31, 2017, 9:07 AM EST - info: [renderer/system-heartbeat] System Heartbeat: New timeoutID:  10
Jan 31, 2017, 9:07 AM EST - info: [main/docker-machine] checked IP 192.168.75.100

Jan 31, 2017, 9:07 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:07 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:07 AM EST - info: [main/startSite] Running start 2b707dbda88296469f3a9f6d6073e435367c9db621e2a045aa54932fc4b4a408
Jan 31, 2017, 9:08 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:08 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:08 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:08 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:08 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:08 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:08 AM EST - info: [main/startSite] Running start 90854a82665d6226cd298f0dd565bb566104013fd4085523bab6e71ae7954529
Jan 31, 2017, 9:08 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:08 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:08 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:08 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }
Jan 31, 2017, 9:09 AM EST - info: [main/check-system] Check System: Checking for Docker Machine
Jan 31, 2017, 9:09 AM EST - info: [main/check-system] Check System: Docker Machine:  
{ stderr: '', stdout: 'Running\n' }

What can I do? Is there a way to recover any of the work that appears to have been lost in the upgrade?

6

@iamblued

Very sorry for the trouble!

Can you please go to ~/Library/Application Support/Local by Flywheel in Finder and provide the contents of the machine.json file?

If it contains local-by-flywheel for the name/image, feel free to change them to pressmatic then restart Local.

7

Here are the contents as they appeared before I did anything:

{
"name": "pressmatic",
"image": "pressmatic"
}

Is there another configuration I should try since it appears your suggestion was already configured.

Thanks for the reply!

8

Can you open VirtualBox.app and check what the VM is named there?

9

Clay,

The name of the VM is pressmatic. See the screenshot for more details as needed:

Oracle_VM_VirtualBox_Manager_and_Cannot_start_any_sites_-_Support_-_Local_by_Flywheel_and_osx.png1542×1146 200 KB

10

Hi Clay,

Any update on this issue? It appears the latest version of Flywheel has removed all my previous Pressmatic sites.

Is the older version of Pressmatic available? Perhaps running the version my older sites were created with might allow me to export them properly to the new version.

Any thoughts and assistance are most appreciated.

11

Hi Peter,

Unfortunately the old version isn’t available.

If it’s showing “No such container” then more than likely the VM was deleted at some point. Do you know if you went into VirtualBox and deleted the Local or Pressmatic VM?