I was the following problems with my VVV installation earlier this year. The following are the steps I took to fix things:
Since November PHP7 is the default for VVV, but at that time (Sept/Oct), it was not. But it was included on the [develop]
branch (not [master]
) of VVV.
- Switch to
[develop]
:git checkout develop
git pull
Shortly after that though (there may have been something else I installed that I overlooked - not necessarily VVV), I started getting the nginx bind()
errors that are shown here in the other file. I used that other method for months to "bypass" my problems, but eventually decided to give it another go at fixing things.
- I updated everything (Vagrant, Virtual Box, VVV, even tried to update the Ubuntu distro, though it failed for various reasons)
- Updated Apple macOS Sierra's
XCode
(one of the updates in the App Store at that time) - Tried to
vagrant up
again, but got multiple different errors - Tried to do a fresh install in a totally NEW
vagrant-new
directory (vagrant-local
was the original) - Tried updating all the
vagrant plugin installs
- Discovered that recent additions to VVV were "breaking changes" and I should do a
git pull
on that branch then avagrant provision
But nothing worked right - I kept getting multiple, various errors.
Finally I found a fix on the VVV GitHub Issues #1043 Mysql unrecognized service. I followed the same steps:
- Manually removed the Vagrant virtual machine from the VirtualBox GUI
- Had to do a
rm -R vagrant-local
in/Users/<username>/VirtualBox VMs/
to recursively remove all the files that I hadn't originally allowed the GUI to delete - Copied
Vagrantfile
in the root directory toVagrantfile.bak
as a backup - Reinitialized Vagrant with
vagrant init
in the root directory - Copied
Vagrantfile.bak
's contents to the newly createdVagrantfile
- Ran
vagrant up
again
This time, FINALLY, everything went totally smoothly! Not a single red error message! Finally! You know how long I've waited to not see red? Wow - big relief. Now, back to dev work~~
Superb man!