Report this

What is the reason for this report?

Rails one-click app and Unicorn

Posted on December 13, 2016

Hi,

We just push a patch on our server. The patch actually require from our Gemfile a git repo using a specific branch as follow:

gem 'valid_email2', github: 'wamland-team/valid_email2', branch: 'feature-mx-whitelist'

When restarting the server, and especially unicorn; we’ve got the following error in the log:

E, [2016-12-12T19:56:39.640894 #30255] ERROR -- : reaped #<Process::Status: pid 30522 exit 1> worker=1
I, [2016-12-12T19:56:39.641112 #30255]  INFO -- : worker=1 spawning...
E, [2016-12-12T19:56:39.805898 #30525] ERROR -- : git://github.com/wamland-team/valid_email2.git (at feature-mx-whitelist) is not yet checked out. Run `bundle install` first. (Bundler::GitError)
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/source/git.rb:192:in `rescue in load_spec_files'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/source/git.rb:189:in `load_spec_files'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/source/path.rb:92:in `local_specs'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/source/git.rb:159:in `specs'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/lazy_specification.rb:53:in `__materialize__'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/spec_set.rb:88:in `block in materialize'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/spec_set.rb:85:in `map!'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/spec_set.rb:85:in `materialize'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/definition.rb:132:in `specs'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/definition.rb:177:in `specs_for'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/definition.rb:166:in `requested_specs'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/environment.rb:18:in `requested_specs'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler/runtime.rb:13:in `setup'
/usr/local/rvm/gems/ruby-2.2.1@global/gems/bundler-1.8.4/lib/bundler.rb:122:in `setup'
/etc/unicorn.conf:10:in `block in reload'

NOTE: We did ran bundle install during the deploy.

Idea? Thanks



This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
0

Ok I solved the issue. There was a problem with an old version of bundler which install the gem under the wrong Ruby version. That was why Unicorn was unable to locate the check out version of my gem. Doing the following:

gem install bundle
bundle install

solved the issue. Hope it will help some folks out there

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.