Angry_Output

mjbrender:vagrant-gswd mjbrender$ vagrant status
Current machine states:

default                   not created (virtualbox)

The environment has not yet been created. Run `vagrant up` to
create the environment. If a machine is not created, only the
default provider will be shown. So if a provider is not listed,
then the machine is not created for that environment.
mjbrender:vagrant-gswd mjbrender$
mjbrender:vagrant-gswd mjbrender$
mjbrender:vagrant-gswd mjbrender$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
[default] Importing base box 'precise64'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] -- 8000 => 8888 (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
prevent things such as shared folders from working properly. If you see
shared folder errors, please make sure the guest additions within the
virtual machine match the version of VirtualBox you have installed on
your host and reload your VM.

Guest Additions Version: 4.2.0
VirtualBox Version: 4.3
[default] Mounting shared folders...
[default] -- /vagrant
[default] -- /tmp/vagrant-chef-1/chef-solo-1/cookbooks
[default] -- /tmp/vagrant-chef-1/chef-solo-2/cookbooks
[default] Running provisioner: shell...
[default] Running: inline script
stdin: is not a tty
Successfully installed mixlib-config-2.1.0
Successfully installed mixlib-cli-1.5.0
Successfully installed mixlib-shellout-1.4.0
Successfully installed ohai-7.0.4
Successfully installed net-ssh-2.9.1
Successfully installed diff-lcs-1.2.5
Successfully installed hashie-2.1.1
Successfully installed rack-1.5.2
Successfully installed chef-zero-2.1.4
Successfully installed coderay-1.1.0
Successfully installed slop-3.5.0
Successfully installed method_source-0.8.2
Successfully installed pry-0.9.12.6
Successfully installed chef-11.12.4
Successfully installed net-ssh-gateway-1.2.0
15 gems installed
[default] Running provisioner: chef_solo...
Generating chef JSON and uploading...
Running chef-solo...
stdin: is not a tty
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/ohai-7.0.4/lib/ohai/loader.rb:188: warning: character class has `[' without escape
/opt/vagrant_ruby/lib/ruby/gems/1.8/gems/ohai-7.0.4/lib/ohai/loader.rb:188: warning: regexp has `]' without escape
[2014-05-31T16:21:55+00:00] INFO: Forking chef instance to converge...
[2014-05-31T16:21:55+00:00] WARN:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
SSL validation of HTTPS requests is disabled. HTTPS connections are still
encrypted, but chef is not able to detect forged replies or man in the middle
attacks.

To fix this issue add an entry like this to your configuration file:

```
  # Verify all HTTPS connections (recommended)
  ssl_verify_mode :verify_peer

  # OR, Verify only connections to chef-server
  verify_api_cert true
```

To check your SSL configuration, or troubleshoot errors, you can use the
`knife ssl check` command like so:

```
  knife ssl check -c /tmp/vagrant-chef-1/solo.rb
```

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

[2014-05-31T16:21:55+00:00] INFO: *** Chef 11.12.4 ***
[2014-05-31T16:21:55+00:00] INFO: Chef-client pid: 1149
[2014-05-31T16:21:58+00:00] INFO: Setting the run_list to ["recipe[postgresql::server_debian]", "recipe[postgresql::ruby]", "recipe[redis::server]", "recipe[git]", "recipe[mercurial]", "recipe[emacs]", "recipe[vim]", "recipe[pip]", "recipe[nano]", "recipe[gswd::database]"] from CLI options
[2014-05-31T16:21:58+00:00] INFO: Run List is [recipe[postgresql::server_debian], recipe[postgresql::ruby], recipe[redis::server], recipe[git], recipe[mercurial], recipe[emacs], recipe[vim], recipe[pip], recipe[nano], recipe[gswd::database]]
[2014-05-31T16:21:58+00:00] INFO: Run List expands to [postgresql::server_debian, postgresql::ruby, redis::server, git, mercurial, emacs, vim, pip, nano, gswd::database]
[2014-05-31T16:21:58+00:00] INFO: Starting Chef Run for precise64
[2014-05-31T16:21:58+00:00] INFO: Running start handlers
[2014-05-31T16:21:58+00:00] INFO: Start handlers complete.
[2014-05-31T16:21:59+00:00] ERROR: Running exception handlers
[2014-05-31T16:21:59+00:00] ERROR: Exception handlers complete
[2014-05-31T16:21:59+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2014-05-31T16:21:59+00:00] ERROR: Cookbook yum-epel not found. If you're loading yum-epel from another cookbook, make sure you configure the dependency in your metadata
[2014-05-31T16:21:59+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.