output.sh

⌘ ~/Sites/vip/ (master) ./bin/vip-init 

 _   __(_)___     ____ ___  __(_)____/ /_______/ /_____ ______/ /_
| | / / / __ \   / __ `/ / / / / ___/ //_/ ___/ __/ __ `/ ___/ __/
| |/ / / /_/ /  / /_/ / /_/ / / /__/ ,< (__  ) /_/ /_/ / /  / /_
|___/_/ .___/   \__, /\__,_/_/\___/_/|_/____/\__/\__,_/_/   \__/
     /_/          /_/


Enter your password to continue:

==================================
= Updating VIP Quickstart
==================================
Already up-to-date.

==================================
= Updating VIP Shared plugins
==================================
Updating 'www/wp-content/themes/vip/plugins':
At revision 127184.

==================================
= Provisioning the VM
==================================
[default] Attempting graceful shutdown of VM...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] -- 3306 => 3306 (adapter 1)
[default] Booting VM...
[default] Waiting for machine to boot. This may take a few minutes...
[default] Machine booted and ready!
[default] The guest additions on this VM do not match the installed version of
VirtualBox! In most cases this is fine, but in rare cases it can
cause things such as shared folders to not work properly. If you see
shared folder errors, please update the guest additions within the
virtual machine and reload your VM.

Guest Additions Version: 4.2.0
VirtualBox Version: 4.3
[default] Setting hostname...
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- /srv
[default] -- /vagrant
[default] -- /tmp/vagrant-puppet/manifests
[default] -- /tmp/vagrant-puppet/modules-0
Bringing machine 'default' up with 'virtualbox' provider...
[default] VirtualBox VM is already running.
[default] Running provisioner: shell...
[default] Running: inline script
stdin: is not a tty
[default] Running provisioner: puppet...
Running Puppet with init.pp...
stdin: is not a tty
notice: /Stage[svn]/Svn/Exec[checkout Minileven]/returns: executed successfully
notice: /Stage[svn]/Svn/Exec[svn up Minileven]/returns: executed successfully
notice: /Stage[updates]/Updates/Exec[apt-get update]/returns: executed successfully
notice: /Stage[svn]/Svn/Exec[svn up WordPress]/returns: executed successfully
notice: /Stage[main]//File[/etc/environment]/content: content changed '{md5}46cce02723b6ef51108614f625974a5f' to '{md5}6df23eb26a479d575824173f29097dfe'
notice: /Stage[main]//Nginx::Vhost[vip.dev]/File[/etc/nginx/sites-available/50-vip.dev.conf]/content: content changed '{md5}65ba499648fe8bdfa33ffe9d86d1f515' to '{md5}46b1d0957f3acfeb68a36ecd0c3d6f58'
err: /Stage[main]/Nginx/Service[nginx]/ensure: change from stopped to running failed: Could not start Service[nginx]: Execution of '/etc/init.d/nginx start' returned 1:  at /tmp/vagrant-puppet/modules-0/nginx/manifests/init.pp:383
notice: /Stage[main]/Nginx/Service[nginx]: Triggered 'refresh' from 1 events
notice: /Stage[main]//Nginx::Vhost[vip.dev]/File[/srv/www]/owner: owner changed 'vagrant' to 'root'
notice: /Stage[main]//Nginx::Vhost[vip.dev]/File[/srv/www]/group: group changed 'vagrant' to 'root'
notice: /Stage[main]//Nginx::Vhost[vip.dev]/File[/srv/www]/mode: mode changed '0755' to '0775'
notice: /Stage[main]/Wp::Cli/File[/usr/bin/wp]/target: target changed '/vagrant/www/wp-cli/bin/wp' to '/srv/www/wp-cli/bin/wp'
notice: /Stage[main]//Exec[wp install /srv/www/wp]/returns: executed successfully
notice: /Stage[main]//Wp::Plugin[developer]/Wp::Command[/srv/www/wp plugin developer enabled]/Exec[wp plugin activate developer --network]/returns: executed successfully
notice: /Stage[main]//Wp::Command[plugin update --all]/Exec[wp plugin update --all]/returns: executed successfully
err: /Stage[main]//Wp::Plugin[jetpack]/Wp::Command[/srv/www/wp plugin jetpack enabled]/Exec[wp plugin activate jetpack --network]/returns: change from notrun to 0 failed: /usr/bin/wp plugin activate jetpack --network returned 255 instead of one of [0] at /tmp/vagrant-puppet/modules-0/wp/manifests/command.pp:12
err: /Stage[main]//Wp::Command[developer install-plugins]/Exec[wp developer install-plugins --type=wpcom-vip --activate]/returns: change from notrun to 0 failed: /usr/bin/wp developer install-plugins --type=wpcom-vip --activate returned 255 instead of one of [0] at /tmp/vagrant-puppet/modules-0/wp/manifests/command.pp:12
notice: /Stage[main]//Wp::Plugin[mrss]/Wp::Command[/srv/www/wp plugin mrss enabled]/Exec[wp plugin activate mrss --network]/returns: executed successfully
notice: Finished catalog run in 46.21 seconds
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

FACTER_svn_username='' FACTER_svn_password='' puppet apply --templatedir /vagrant/puppet/files --modulepath '/etc/puppet/modules:/tmp/vagrant-puppet/modules-0' --manifestdir /tmp/vagrant-puppet/manifests --detailed-exitcodes /tmp/vagrant-puppet/manifests/init.pp || [ $? -eq 2 ]

Stdout from the command:

notice: /Stage[svn]/Svn/Exec[checkout Minileven]/returns: executed successfully
notice: /Stage[svn]/Svn/Exec[svn up Minileven]/returns: executed successfully
notice: /Stage[updates]/Updates/Exec[apt-get update]/returns: executed successfully
notice: /Stage[svn]/Svn/Exec[svn up WordPress]/returns: executed successfully
notice: /Stage[main]//File[/etc/environment]/content: content changed '{md5}46cce02723b6ef51108614f625974a5f' to '{md5}6df23eb26a479d575824173f29097dfe'
notice: /Stage[main]//Nginx::Vhost[vip.dev]/File[/etc/nginx/sites-available/50-vip.dev.conf]/content: content changed '{md5}65ba499648fe8bdfa33ffe9d86d1f515' to '{md5}46b1d0957f3acfeb68a36ecd0c3d6f58'
err: /Stage[main]/Nginx/Service[nginx]/ensure: change from stopped to running failed: Could not start Service[nginx]: Execution of '/etc/init.d/nginx start' returned 1:  at /tmp/vagrant-puppet/modules-0/nginx/manifests/init.pp:383
notice: /Stage[main]/Nginx/Service[nginx]: Triggered 'refresh' from 1 events
notice: /Stage[main]//Nginx::Vhost[vip.dev]/File[/srv/www]/owner: owner changed 'vagrant' to 'root'
notice: /Stage[main]//Nginx::Vhost[vip.dev]/File[/srv/www]/group: group changed 'vagrant' to 'root'
notice: /Stage[main]//Nginx::Vhost[vip.dev]/File[/srv/www]/mode: mode changed '0755' to '0775'
notice: /Stage[main]/Wp::Cli/File[/usr/bin/wp]/target: target changed '/vagrant/www/wp-cli/bin/wp' to '/srv/www/wp-cli/bin/wp'
notice: /Stage[main]//Exec[wp install /srv/www/wp]/returns: executed successfully
notice: /Stage[main]//Wp::Plugin[developer]/Wp::Command[/srv/www/wp plugin developer enabled]/Exec[wp plugin activate developer --network]/returns: executed successfully
notice: /Stage[main]//Wp::Command[plugin update --all]/Exec[wp plugin update --all]/returns: executed successfully
err: /Stage[main]//Wp::Plugin[jetpack]/Wp::Command[/srv/www/wp plugin jetpack enabled]/Exec[wp plugin activate jetpack --network]/returns: change from notrun to 0 failed: /usr/bin/wp plugin activate jetpack --network returned 255 instead of one of [0] at /tmp/vagrant-puppet/modules-0/wp/manifests/command.pp:12
err: /Stage[main]//Wp::Command[developer install-plugins]/Exec[wp developer install-plugins --type=wpcom-vip --activate]/returns: change from notrun to 0 failed: /usr/bin/wp developer install-plugins --type=wpcom-vip --activate returned 255 instead of one of [0] at /tmp/vagrant-puppet/modules-0/wp/manifests/command.pp:12
notice: /Stage[main]//Wp::Plugin[mrss]/Wp::Command[/srv/www/wp plugin mrss enabled]/Exec[wp plugin activate mrss --network]/returns: executed successfully
notice: Finished catalog run in 46.21 seconds


Stderr from the command:

stdin: is not a tty


==================================
= Configuring the hosts file
==================================
10.86.73.80 vip.dev

==================================
= Next Steps
==================================
* Go to http://vip.dev in your browser