Stuck on login about vagrant_demo

[jeremyquinton]

If you run it with --no-provision you should then be able to run vagrant ssh from the command line to login to the box. Once logged in you can run "sudo su" to get root access. If you want to login on the gui vagrant boxes but default have a username and password of vagrant, vagrant. Sudo su will give you root access. Looking at the exception it looks there is a problem with the epel repository. I'll try provision the box locally and then get back to.

[jeremyquinton]

I updated the epel repo to version 6.8. If you do an update on the project and run vagrant up so that it runs the provisioning you shouldn't get any errors.

[bizmate]

Thanks for the quick reply. I saw another minor error i guess, since i can ssh fine on the machine. I just had another question, i did try to load 33.33.33.10 or vagrantdemo.com after adding it on the host machine /etc/hosts but for some reason it looks like apache is not loading. Was the machine supposed to autostart apache and mysql or should i still install mysql etc, it looks like they are not installed when i look for them on the machine

Here is the logs of the vagrant up --no-provision

vagrant up --no-provision
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/hosts/bsd.rb:32: warning: Insecure world writable dir /usr/local/bin in PATH, mode 040777
[default] Importing base box 'vagrant-centos-6.3'...
[default] The guest additions on this VM do not match the install version of
VirtualBox! This may cause things such as forwarded ports, shared
folders, and more to not work properly. If any of those things fail on
this machine, please update the guest additions and repackage the
box.

Guest Additions Version: 4.1.22
VirtualBox Version: 4.2.6
[default] Matching MAC address for NAT networking...
[default] Clearing any previously set forwarded ports...
[default] Fixed port collision for 22 => 2222. Now on port 2200.
[default] Forwarding ports...
[default] -- 22 => 2200 (adapter 1)
[vagrant] Pruning invalid NFS exports. Administrator privileges will be required...
Password:
[default] Exporting NFS shared folders...
[vagrant] Preparing to edit /etc/exports. Administrator privileges will be required...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/sbin/ifup eth1 2> /dev/null

---

I wonder if i should do something in virtualbox to fix the connectivity and SSH error above

[bizmate]

Never mind the ssh error, i had another vm running using the previous settings so there was some collision. I did destroy the previous vm and destroyed and upped the one with the new conf you just commit. However i am still getting chef related errors ...

vagrant up
/Applications/Vagrant/embedded/gems/gems/vagrant-1.0.6/lib/vagrant/hosts/bsd.rb:32: warning: Insecure world writable dir /usr/local/bin in PATH, mode 040777
[default] Importing base box 'vagrant-centos-6.3'...
[default] The guest additions on this VM do not match the install version of
VirtualBox! This may cause things such as forwarded ports, shared
folders, and more to not work properly. If any of those things fail on
this machine, please update the guest additions and repackage the
box.

Guest Additions Version: 4.1.22
VirtualBox Version: 4.2.6
[default] Matching MAC address for NAT networking...
[default] Clearing any previously set forwarded ports...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[vagrant] Pruning invalid NFS exports. Administrator privileges will be required...
[default] Exporting NFS shared folders...
[vagrant] Preparing to edit /etc/exports. Administrator privileges will be required...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] -- v-root: /vagrant
[default] -- v-csr-2: /tmp/vagrant-chef-1/chef-solo-2/roles
[default] -- v-csc-1: /tmp/vagrant-chef-1/chef-solo-1/cookbooks
[default] Mounting NFS shared folders...
[default] Running provisioner: Vagrant::Provisioners::ChefSolo...
[default] Generating chef JSON and uploading...
[default] Running chef-solo...
[2013-01-16T01:07:57+00:00] INFO: *** Chef 10.16.2 ***
[2013-01-16T01:07:58+00:00] INFO: Setting the run_list to ["role[local]"] from JSON
[2013-01-16T01:07:58+00:00] INFO: Run List is [role[local]]
[2013-01-16T01:07:58+00:00] INFO: Run List expands to [yum::ius, hostsfile-writer, iptables-writer, mysql::server, apache2, apache2::mod_deflate, apache2::mod_rewrite, apache2::mod_expires, apache2::mod_headers, apache2::vagrant_demo, php, php::module_mysql, composer]
[2013-01-16T01:07:58+00:00] INFO: Starting Chef Run for localhost
[2013-01-16T01:07:58+00:00] INFO: Running start handlers
[2013-01-16T01:07:58+00:00] INFO: Start handlers complete.
[2013-01-16T01:07:58+00:00] WARN: Setting attributes without specifying a precedence is deprecated and will be
removed in Chef 11.0. To set attributes at normal precedence, change code like:
node["key"] = "value" # Not this
to:
node.set["key"] = "value" # This

Called from:
/usr/lib/ruby/gems/1.8/gems/chef-10.16.2/bin/../lib/chef/node/attribute.rb:449:in method_missing' /usr/lib/ruby/gems/1.8/gems/chef-10.16.2/bin/../lib/chef/node.rb:346:insend'
/usr/lib/ruby/gems/1.8/gems/chef-10.16.2/bin/../lib/chef/node.rb:346:in `method_missing'

[2013-01-16T01:07:59+00:00] INFO: Could not find previously defined grants.sql resource
[2013-01-16T01:07:59+00:00] ERROR: Running exception handlers
[2013-01-16T01:07:59+00:00] ERROR: Exception handlers complete
[2013-01-16T01:07:59+00:00] FATAL: Stacktrace dumped to /tmp/vagrant-chef-1/chef-stacktrace.out
[2013-01-16T01:07:59+00:00] FATAL: Chef::Exceptions::CookbookNotFound: Cookbook composer not found. If you're loading composer from another cookbook, make sure you configure the dependency in your metadata
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

[bizmate]

Just another quick comment, i did check your pv project. It works better than this one at the moment for me.
I had to fix the default['yum']['epel_release'] to include the 6-8 file rather than 6-7.
At the moment i get a forbidden response from vagrantdemo.com but i guess i can now work out why and set up my vhosts

[jeremyquinton]

I committed the run list with the composer recipe but did not commit the recipe in the cookbooks folder which is what caused the error. If you get the latest version of the project and try it you shouldn't get any errors. As for the forbidden error if you add the 33.33.33.10 vagrantdemo.com to /etc/hosts the virtualhost should work straight away. https://github.com/jeremyquinton/vagrant_demo/blob/master/cookbooks/apache2/recipes/vagrant_demo.rb creates the default virtual host on the virtual machine. I would perhaps destroy the vagrant machine and rebuild it from scratch. What host operating system are you using?

[bizmate]

Thanks again for looking into it. The vagrant_demo project works for me now. About the pv project even if i add the entry in the /etc/hosts still i get the forbidden page
I am on a macbook air 10.7.5