Vvv: Fresh and only clone of VVV not working on Mac OSX

[ghost]

I followed the instructions here to the letter. However, when I visit http://vvv.dev/ or any of the default sites like http://local.wordpress.dev/, I get a "This webpage is not available" response.

I have multiple multisite setups running on VVV on my Ubuntu machine and everything works fine. I just recently started using a MacBook Pro but for some reason a fresh start with VVV is giving me headache. Please help.

Here's what I get on my terminal:

Doms-MacBook-Pro:firebirds domsmariano$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: There was a problem while downloading the metadata for your box
==> default: to check for updates. This is not an error, since it is usually due
==> default: to temporary network problems. This is just a warning. The problem
==> default: encountered was:
==> default: 
==> default: Couldn't resolve host 'vagrantcloud.com'
==> default: 
==> default: If you want to check for box updates, verify your network connection
==> default: is valid and try again.
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
    default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Checking for host entries
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => /Users/domsmariano/Desktop/firebirds
    default: /srv/www => /Users/domsmariano/Desktop/firebirds/www
    default: /srv/log => /Users/domsmariano/Desktop/firebirds/log
    default: /srv/config => /Users/domsmariano/Desktop/firebirds/config
    default: /srv/database => /Users/domsmariano/Desktop/firebirds/database
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: to force provisioning. Provisioners marked to run always will still run.
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: mysql: unrecognized service
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.
Doms-MacBook-Pro:firebirds domsmariano$ 

[ghost]

Nevermind. I just destroyed the whole thing and started over again.

[simme]

I am getting the same thing.. trying again does not seem to help:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: VirtualBox VM is already running.
==> default: Checking for host entries
~/Projects/vagrant-local/ master
λ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/trusty64' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Checking for host entries
==> default: Setting hostname...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => /Users/simme/Projects/vagrant-local
    default: /srv/www => /Users/simme/Projects/vagrant-local/www
    default: /srv/log => /Users/simme/Projects/vagrant-local/log
    default: /srv/config => /Users/simme/Projects/vagrant-local/config
    default: /srv/database => /Users/simme/Projects/vagrant-local/database
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: to force provisioning. Provisioners marked to run always will still run.
==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: mysql: unrecognized service
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

[ghost]

@simme Yes I get this same "mysql: unrecognized service" error, I'm also on latest mac osx with all dependencies installed and VVV freshly installed yesterday. To add, I've used VVV a lot on this machine and have never run into this issue before.

[ghost]

@simme vagrant reload --provision fixed it for me, not sure why it didn't work on first vagrant up but alas it now works again : )

[JJJ]

I think this happens when trying to do-release-upgrade inside the VM.

That leaves a few binaries in limbo, namely mysql and grunt in my experience.