Stuck on "Checking System..."

On my mac - hanging at “checking system …” (3.2.1 localby =flywheel version)
nothing extra mentioned, this happened after i did not use the app for a week or 2

  • any suggestions how to solve this ?

i emoved the app and reinstalled - that did not help -
Unfortunately i have no clue where all files are kept on the mac

It did all work before after i installed it so i suspect an update wrecked i?

ok i accidently deleted virtual box afther re-instaling virtual box again it worked

local-by-flywheel.log (29.1 KB)

I have been using Local BF for about a week now then this suddenly happened when I reopened a project.
On my mac - hanging at “checking system”
Removed and reinstalled both Local BF and Virtual Box.
Any suggestions would be great.

I experienced Checking System also., local-by-flywheel.log (6.3 KB)

Hey @rodcel

In your Local log, I’m seeing this occuring multiple times:

Jul 19, 2019, 3:55 PM CDT - warn: [main/index] Unhandled Rejection at: Promise  Promise {
  <rejected> { Error: ETIMEDOUT

That makes me think there is some sort of issue with the Docker daemon inside the Virtual Machine. Can you try restarting the VM by going to “Help > Restart Local Machine”.

If that doesn’t work, then follow the steps outlined in this topic to forcefully shut down and restart the VM:

@zeke – Your Local log has a different error that looks like:

Jul 22, 2019, 9:09 PM GMT+8 - info: [main/check-system] Check System: Docker Machine:  
{ stdout: '',
  stderr:
   'Error getting migrated host: invalid character \'\\x00\' looking for beginning of value\n' }

I found this Github thread: https://github.com/docker/for-linux/issues/140

Which seems to indicate that it might be due to some invalid characters within the Docker Logs. Was there a recent upgrade to the Host operating system? Are you using docker for other projects outside of Local?

local-by-flywheel.log (92.3 KB)

Hey @Florence

I’m seeing a few instances of this in the Local Log:

Jul 24, 2019, 3:14 PM GMT+2 - info: [main/check-system] Check System: Docker Machine:  
{ stdout: '',
  stderr:
   'error getting state for host local-by-flywheel: exit status 126\n' }

That makes me think there is some sort of issue with the Docker daemon inside the Virtual Machine. Can you try restarting the VM by going to “Help > Restart Local Machine”.

If that doesn’t work, then follow the steps outlined in this topic to forcefully shut down and restart the VM:

Thanks a lot, I could solve the problem

@ben.turner Thanks for the reply!

The local log has the following error:

Aug 5, 2019, 9:59 AM CDT - info: [main/check-system] Check System: Docker Machine:  
{ stdout: ' ',
  stderr:
   'Error getting migrated host: unexpected end of JSON input\n' }

I went through the thread and could not identify or locate any invalid characters resembling those above.

I did upgrade to Mojave recently but errors were present prior to upgrading. Docker is not being used for other projects.

Thanks again for taking the time to read and respond to these messages.

Hey @zeke

We’ve had a couple more people write in about the original error that I saw in the Local log:

Error getting migrated host: invalid character \'\\x00\'

In some cases it’s due to a corrupted configuration file. Can you take a look at the solution that was given in this thread and see if it fixes things for you?

it started when i installed it for the first time, i have tried unstalling and again reinstalling it . but still it is stuck on ‘checking system’. please suggest me solution to eliminate this issue

thank you.

Hey @adg15

When you uninstalled Local, did you follow the steps that are outlined here:

Those instructions should lead you to completely removing Local along with any configuration files that might be left behind.

Can you retry re-installing Local by first uninstalling using one of the above links?

local-by-flywheel.log (12.7 KB) Here is my Log on Windows. Had problems with new update. Uninstalled (followed directions), no jive. Reinstalled still stuck.

nevermind got it corrupted .docker file was the problem

local-by-flywheel.log (6.1 KB)

Same problem here (macOS Mojave), @ben.turner can you help me? Thank you

Hey @marcoluciani

Your local log has this contained within it:

error getting state for host local-by-flywheel: exit status 126

This usually means that something within the virtual machine is crashing. Can you try restarting the VM by going to “Help > Restart Local Machine”.

If that doesn’t work, then follow the steps outlined in this topic to forcefully shut down and restart the VM:

FIXED

Thanks Ben! Your suggestion below worked a treat.

All I did was re-download VirtualBox from the link below, restarted Local again, and it worked. Still took a while to load, but gave it a couple of minutes to do it’s thing and it was fine.

https://www.virtualbox.org/wiki/Downloads

I don’t know if it makes a difference—probably not—but after installing VirtualBox, I opened it and left it open. Probably nothing, but you do tend to clutch at straws when things like this happen, so worth saying.

1 Like

I ran into the same issue on my Mac.
What worked for me (I don’t know why but it did :stuck_out_tongue:) was:

  • Quit Local By Flywheel
  • start virtualbox (manager) and start the VM
  • Wait for the VM to be fully booted
  • Start Local By Flywheel (for some reason this made the VM shutdown)
  • Local By Flywheel got stuck again so I quit it and restarted it

Like I said, I have no idea why this happened or why the fix worked but it did.

Hopefully this helps out someone else with the same issue.

I had it running sound then finally had to reside to fact to upgrade to Windows 10 (still for free if you need to know :)) - Then run into same problems - so I downloaded Virtual Box Re-Installed Local by Flywheel and Voilla it works - the only problem I having now is some errors on Importing my local sites I saved with 3 in one migration but sorted it out somehow last time so sure it will work out - main thing is I can now work locally again.

Hope this helps anyone needing!