Varying Vagrant Vagrants logo Varying Vagrant Vagrants

Need help?

Starting from Fresh

Sometimes, a clean fresh start fixes things, to do this, run the following commands:

# make sure this is the latest VVV
git pull
# Turn off the machine
vagrant halt
# Destroy the machine
vagrant destroy
# Make sure we use the latest version of the base box§
vagrant box update
# Make sure the recommended vagrant plugins are installed
vagrant plugin install vagrant-triggers vagrant-vbguest vagrant-hostsupdater
# And that they're all up to date
vagrant plugin update
# Start VVV and create the VM from scratch
vagrant up --provision

Common Problems

SSH Timeout During Provision

This is a generic error that can indicate multiple things, including:

If this happens, do the following, and provide the results when asking for help.

Vagrant Plugin Install Issues and Broken Vagrant Upgrades

When updating from Vagrant 1.x to 2.x, Vagrants bundler can throw errors, here’s an example:

$ vagrant plugin install vagrant-triggers vagrant-vbguest vagrant-hostsupdater
Installing the 'vagrant-triggers' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies ffi (= 1.9.18) and ffi (= 1.9.14)
  Activated ffi-1.9.14
  which does not match conflicting dependency (= 1.9.18)

  Conflicting dependency chains:
    ffi (= 1.9.14), 1.9.14 activated

  versus:
    ffi (= 1.9.18)

  Gems matching ffi (= 1.9.18):
    ffi-1.9.18-x64-mingw32

When this happens, the solution is to completely uninstall Vagrant, then reinstall. Do this either using the uninstall tool in the DMG on MacOS, or the standard uninstaller on Windows.

Corrupt VM

It’s possible that the Virtual Machine file system may become corrupted. This might happen if your VM didn’t shut down correctly, perhaps there was a power cut or your laptop ran out of power unexpectedly.

In this scenario, your files should be safe on the host filesystem. If the Vagrant triggers plugin is installed, a database backup will be available. Using these, the site can be recovered from a fresh VVV box.

Run vagrant halt; vagrant destroy to delete the Virtual Machine, followed by vagrant up --provision to recreate the machine. When the process is finished, restore the database from backups.

For more information on backups, see the backups section below.

Common Causes of Problems

Typos in vvv-custom.yml

If there’s a typo or syntax error in vvv-custom.yml the provisioner will fail. Make sure the file is valid YAML when making changes to this file.

Out of Date VVV

VVV is an active project, but if it isn’t up to date you might suffer from bugs that have already been fixed. Do a git pull and restart/reprovision VVV. If you download a zip instead, you can go to the install instructions for commands to convert your install to use git.

Out of Date Software

Mismatched Virtualbox and Guest additions can cause problems, as can older versions of Vagrant. When troubleshooting a problem, update to the latest versions of software, then verify the problem still exists after a vagrant halt;vagrant up --provision

Local Network IP Clashes

The network configuration picks an IP of 192.168.50.4. It could cause conflicts on your existing network if you are on a 192.168.50.x subnet already. You can configure any IP address in the Vagrantfile and it will be used on the next vagrant up --provision

Vagrant and VirtualBox

VVV relies on the stability of both Vagrant and VirtualBox. These caveats are common to Vagrant environments and are worth noting:

Memory Allotment

The default memory allotment for the VVV virtual machine is 1024MB. If you would like to raise or lower this value to better match your system requirements, a you can do so with the vm_config section of vvv-custom.yml is in the wiki.

64bit Ubuntu and Older CPUs

Since version 1.2.0, VVV has used a 64bit version of Ubuntu. Some older CPUs (such as the popular Intel Core 2 Duo series) do not support this. Changing the line config.vm.box = "ubuntu/trusty64" to "ubuntu/trusty32" in the Vagrantfile before vagrant up will provision a 32bit version of Ubuntu that will work on older hardware.

Backups

In the event that you’re stuck or at a loss, VVV tries to generate database backups at VVV/database/backups/*.sql, with a file for each database.

This coupled with the uploads in the file system should allow the VVV environment to be recreated from a clean slate.