Knowledge Base/Engine Yard Local/Engine Yard Local Feature Requests

PlannedDoneNot planned

Support for latest Vagrant, VirtualBox and Mac OS X 10.8?

GreenStack Operations
suggested this on October 31, 2012 09:13 AM

We're vagrant fans here and are excited about using ey-local. Alas, updating to OS X 10.8 requires latest VirtualBox (4.2.x), and ey-local is unhappy with anything other than 4.0, 4.1 per:

 

[ey-local] ey-local has detected that you have a version of VirtualBox installed
that is not supported. Please install one of the supported versions
listed below to use Vagrant:

4.0, 4.1

 

We can't downgrade at this point as we are using other critical tools in this environment. Any quick patch in progress or is there anything we can help with?

 

EDIT: I realize vagrant 1.0.5 (latest as of this writing?) works fine with current VirtualBox, so this is mostly solving for dependencies within ey-local perhaps?

 

-Chris Haupt

-GreenStack.com

 

Comments

User photo
Josh Hamilton
Engine Yard Inc.

Hi Chris,

Thanks for the feedback. We're currently working on a new release of EY Local and look to have it out in the next few weeks. I've forwarded this bug to our Engineers and we hope to address this in the new release.

Thanks again,

Josh

October 31, 2012 10:49 AM
User photo
Josh Hamilton
Engine Yard Inc.

Hi Chris,

We pushed the latest version of engineyard-local this morning. We upgraded Vagrant to 1.0.5, which will work with the latest VirtualBox. Let us know if there are any other issues.

Thanks,

Josh

November 15, 2012 09:18 AM
User photo
Michael Jabbour
SelectHW

Hi Josh, VirtualBox 3 seems to be incompatible with eyLocal gem. Any way to correct that?

 

[ey-local] ey-local has detected that you have a version of VirtualBox installed

that is not supported. Please install one of the supported versions

listed below to use Vagrant:

 

4.0, 4.1, 4.2

 

Thanks!

November 05, 2013 10:45 PM
User photo
Michael Jabbour
SelectHW

After downgrading to the latest version of VB (2.8), it downloaded and get to using /.... as application directory.

 

[ey-local] There was a problem with the configuration of Vagrant. The error message(s)

are printed below:

vm:* Base MAC address for eth0/NAT must be set. Contact box maintainer for more information.

November 05, 2013 10:50 PM
User photo
Christopher Rigor
Engine Yard Inc.

Michael,


Can you try running ey-local up again? That error shouldn't appear the second time you run ey-local.

November 05, 2013 11:02 PM
User photo
Michael Jabbour
SelectHW

Hi Chris,

It seemed to run, but then show this message in red:

 

[default] * Please note that the standard location of the socket has changed from /tmp to

[default] * /var/run/postgresql and you have to be in the 'postgres' group to access the

[default] * socket. This can break applications which have the standard location

[default] * hard-coded. If such an application links against the libpq, please reemerge

[default] * it. If that doesn't help or the application accesses the socket without using

[default] * libpq, please file a bug-report.

[default] *

[default] * You can set PGOPTS='-k /tmp' in /etc/conf.d/postgresql-9.1 to restore the

[default] * original location.

[default] *

 

Then later, an subsequent failure:

 

[default] Unfortunately, a fatal error has occurred. Please report this error to the Bundler issue tracker at https://github.com/carlhuda/bundler/issues so that we can fix it. Thanks!

[default] /usr/lib64/ruby/site_ruby/1.9.1/rubygems/installer.rb:552:in `rescue in block in build_extensions': ERROR: Failed to build gem native extension. (Gem::Installer::ExtensionBuildError)

 

        /usr/bin/ruby19 extconf.rb 

checking for Ruby version >= 1.8.5... yes

checking for x86_64-pc-linux-gnu-gcc... yes

checking for Magick-config... yes

checking for ImageMagick version >= 6.4.9... no

Can't install RMagick 2.13.2. You must have ImageMagick 6.4.9 or later.

 

*** extconf.rb failed ***

Could not create Makefile due to some reason, probably lack of

necessary libraries and/or headers.  Check the mkmf.log file for more

details.  You may need configuration options.

 

Provided configuration options:

--with-opt-dir

--without-opt-dir

--with-opt-include

--without-opt-include=${opt-dir}/include

--with-opt-lib

--without-opt-lib=${opt-dir}/

--with-make-prog

--without-make-prog

--srcdir=.

--curdir

--ruby=/usr/bin/ruby19

 

 

Gem files will remain installed in /usr/lib64/ruby/gems/1.9.1/gems/rmagick-2.13.2 for inspection.

Results logged to /usr/lib64/ruby/gems/1.9.1/gems/rmagick-2.13.2/ext/RMagick/gem_make.out

from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/installer.rb:530:in `block in build_extensions'

from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/installer.rb:505:in `each'

from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/installer.rb:505:in `build_extensions'

from /usr/lib64/ruby/site_ruby/1.9.1/rubygems/installer.rb:180:in `install'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/source.rb:90:in `block in install'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/rubygems_integration.rb:82:in `preserve_paths'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/source.rb:89:in `install'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/installer.rb:73:in `block in install_gem_from_spec'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/rubygems_integration.rb:97:in `with_build_args'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/installer.rb:72:in `install_gem_from_spec'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/installer.rb:56:in `block in run'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/installer.rb:55:in `run'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/installer.rb:12:in `install'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/cli.rb:220:in `install'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/vendor/thor/task.rb:22:in `run'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/vendor/thor/invocation.rb:118:in `invoke_task'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/vendor/thor.rb:263:in `dispatch'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/lib/bundler/vendor/thor/base.rb:386:in `start'

from /usr/lib64/ruby/gems/1.9.1/gems/bundler-1.1.0/bin/bundle:13:in `<top (required)>'

from /usr/bin/bundle:19:in `load'

from /usr/bin/bundle:19:in `<main>'

[ey-local] The following SSH command responded with a non-zero exit status.

ey-local assumes that this means the command failed!

 

source /etc/profile.d/*;

export RVM_RUBY=`rvm list | grep "^   " | awk '{ print $1 }' | tail -1`;

rvm use $RVM_RUBY > /dev/null;

sudo bash -c 'command -v bundle &>/dev/null || { sudo gem install bundler; exit 0; }';

cd /vagrant;

sudo mkdir -p /ey-local /data/eripme/;

if [[ ! -e /data/eripme/current ]]; then sudo ln -sf /ey-local /data/eripme/current; fi;

if [[ ! -e /data/eripme/current/public ]]; then sudo mkdir -p /data/eripme/current/public; fi;

if [[ -e Gemfile || -e Gemfile.lock ]]; then sudo bundle install; fi

November 05, 2013 11:14 PM
User photo
Christopher Rigor
Engine Yard Inc.

Can you put the full output in a gist? The rmagick error is due to an old imagemagick version. Try upgrading to the latest version. You may need to unmask the package. Edit /usr/local/package.keywords/local, add =media-gfx/imagemagick-6.7.8.8-r1.

 

You can check the correct version by running eix imagemagick.

November 05, 2013 11:22 PM
User photo
Michael Jabbour
SelectHW

Damn imagemagick, its relentless!

 

https://gist.github.com/softilluminations/1b7521b9e085a95a0d88

 

Thanks!

November 05, 2013 11:30 PM
User photo
Christopher Rigor
Engine Yard Inc.

The postgres message looks like a warning. The postgres recipe succeeded. Are you seeing any issue? I'll ask our DBAs to take a look at the warning.

November 05, 2013 11:57 PM
User photo
Michael Jabbour
SelectHW

The last error looked to me to be a fatal error. I am not certain yet how to utilize EY local, is there information on how to use it? so I just do ey-local rails s to start it?

 

Just added it to the gist thread: https://gist.github.com/softilluminations/1b7521b9e085a95a0d88

 

Thanks,

November 06, 2013 12:17 AM
User photo
Michael Jabbour
SelectHW

Just found this [https://support.cloud.engineyard.com/entries/22355466-Engine-Yard-L... successfully loaded todo app. Since its just my app thats not working, how can I troubleshoot it from here?

 

Thanks!

November 06, 2013 12:51 AM
User photo
Christopher Rigor
Engine Yard Inc.

Michael, are you still having issues with Engine Yard Local? You'll need to update imagemagick to install rmagick 2.13.2.

December 03, 2013 10:30 PM