search

ReliveRadio / reliveradio-plantasy

ReliveRadio Radioautomation auf Ruby on Rails Basis
www.reliveradio.de
2 stars 0 forks source link

setting up test environment #1

Closed germanstudent closed 9 years ago

germanstudent commented 10 years ago

I'm trying to set up the develop branch in a test environment, I think it fails with the ssh key exchange.

I did not modify anything in vagrant, so vagrant up uses the $HOME/.vagrant.d/insecure_private_key I think.

Is there more configuration necessary before vagrant up? Or are VT-x cpu features mandatory for running this VM?

test environment

output

stdout

http://pastebin.com/fG1xBQXf

stderr

http://pastebin.com/Y4rT3C9K

virtual box log

http://pastebin.com/CU6kTCmu

funkenstrahlen commented 10 years ago

Hm, actually this has nothing to do with my configuration as chef starts to provision the VM after it has established an ssh connection. I never had this issue.

Google is full with errors like that: https://www.google.de/search?q=vagrant+default:+Error:+Connection+timeout.+Retrying...&oq=vagrant+default:+Error:+Connection+timeout.+Retrying...&aqs=chrome..69i57.1157j0j7&sourceid=chrome&espv=210&es_sm=91&ie=UTF-8&sei=wIIxU6WLOorb7Aabr4CABA&gbv=2

Maybe this is a good idea to debug the problem: https://stackoverflow.com/questions/22575261/vagrant-stuck-connection-timeout-retrying

In Vagrantfile:

config.vm.provider :virtualbox do |vb|
    vb.gui = true
end

You could also try to launch the VM through the Virtualbox GUI. It should appear there after creation. Just try booting it up and see why it does not start up the ssh.

funkenstrahlen commented 10 years ago

any news on this one?

germanstudent commented 10 years ago

Hey i42n,

sorry for the missing feedback :/

Today I tried to set up the current development branch, unfortunately I failed.

The error mentioned above is because the current virtualbox setup / image requires access to vt-x cpu features and my test server doesn't support this. I tried to disable hardware virtualization by adding this

config.vm.provider :virtualbox do |vb|
  vb.customize ["modifyvm", :id, "--hwvirtex", "off"]
end

to the Vagrantfile, but the image still wouldn't boot.

I finally tested it on two different non virtualized environments so the image would boot sucessfully but the configuration would fail, this is the INFO output of vagrant up

http://pastebin.com/61HyJV9K

I'm not sure, might this be the cause? (from the output above)

INFO interface: info: [2014-04-13T01:54:16+00:00] ERROR: bash[compile_nginx_source] (nginx::source line 97) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
[2014-04-13T01:54:16+00:00] ERROR: bash[compile_nginx_source] (nginx::source line 97) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'

I then connected to the VM manually and tried bundle in the app folder anyway. This lead to the error 

vagrant@vagrant:~/app$ bundle
Fetching source index from https://rubygems.org/
Could not find thread_safe-0.3.0 in any of the sources

I think this is because 3.0 got yanked http://rubygems.org/gems/thread_safe/versions

I tried gem uninstall thread_safe so that bundle worked.

bundle exec sidekiq or rake db:migrate didn't work because of missing dependencies or files. :/

Unfortunately I don't have an in depth knowledge of the code yet and thought you can give a few hints, what's the best way to get this going.

One question: Is it easy to switch to a 32bit ubuntu image? If I'm not mistaken only the 64bit version requires VT-x features. This way we could use cloud instances to quickly set up a testing environments. e.g. this one http://opscode-vm-bento.s3.amazonaws.com/vagrant/virtualbox/opscode_ubuntu-12.04-i386_chef-provisionerless.box listed here: https://github.com/opscode/bento

funkenstrahlen commented 10 years ago

I am sorry that this is such a mess :/ Did not expect that when setting up chef with vagrant. Worked so easy on my machine.

Of course you can use different images. Normally chef should be flexible enough.

Nginx has to compiled manually because of the passenger extension.

Maybe it is too early to setup a test environment. So many details to consider, so many bugs...

If you just want to see the current interface (no mpd connection) you can simply do bundle and rails server in the app folder on your machine. But be aware that the app currently crashes of no mpd is there. Very early prototyp code...

funkenstrahlen commented 10 years ago

If you habe dependency problems try bundle update that helps sometimes.

funkenstrahlen commented 9 years ago

Closed as we use chef + capistrano now.