Puppet failuresEdit

If Puppet fails to configure your machine, vagrant up will terminate with the following error message:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cd /tmp/vagrant-puppet/manifests && puppet apply --verbose --modulepath '/tmp/vagrant-puppet/modules-0' site.pp --detailed-exitcodes || [ $? -eq 2 ]

This error may be caused by run-time failure to connect to Ubuntu package repositories or Gerrit. In such cases, you can simply trigger another Puppet run by running vagrant provision.

If your problem persists, collect detailed information using PUPPET_DEBUG=1 vagrant provision and attach to a new bug report in Phabricator.

Vagrant / VirtualBox failuresEdit

In general, Vagrant and VirtualBox get along quite well. Once in a blue moon, a VM crash in a way that causes Vagrant to lose the ability to manage the machine or inspect its status. If this should happen, you can usually fix things by running VirtualBox's management console and rebooting the machine there.

Some users may see an error:

VT-x features locked or unavailable in MSR. (VERR_VMX_MSR_LOCKED_OR_DISABLED). Result Code: NS_ERROR_FAILURE (0x80004005)

upon trying to bring up the MediaWiki VM.

Click settings, accept the recommended change, and discover that the VM image is 40G in size and a FAT filesystem only supports files up to 16G in size. VirtualBox suggests a filesystem such as ext3 with sufficient size for image files.

Connection failuresEdit

If you try to connect to http://localhost:8080 and you can't connect:

  • Is your Vagrant VM up and running?
  • Do you have any other proxies setup on port 8080?
  • Are there any other browser add-ons, plugins, or proxies wired up that could interfere with connections to localhost?
  • Do you have the Xdebug settings in place, but no tool to intercept the Xdebug connect back calls for PHP scripts?
  • Have you tried...
    • From within a vagrant ssh session, sudo apachectl restart?
    • From your host a vagrant halt and vagrant up?
    • Stashing any file changes you've made in the code and running the pristine code?

If you're trying to connect to while offline:

  • Make sure to have the following in your /etc/hosts file (outside the VM). Edit by running sudo $EDITOR /etc/hosts
# Access MediaWiki-Vagrant when offline

Updating guest additionsEdit

After updating mediawiki-vagrant to the latest version, you might get a random error like "The following SSH command responded with a non-zero exit status." To fix this, you should update your guest additions.

vagrant ssh
cd /tmp
sudo su #need to be root
cd guest-additions.* # the ending is going to be some random string of characters
./ install

The last command may end with "Installing the Window System drivers!", but that's ok. Now you should log out of vagrant, and run vagrant halt and vagrant up!