You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm writing a wrapper cookbook for my web app (using berkshelf and vagrant—if it makes a difference), and when I run vagrant provision, chef-solo fails when trying to install jruby-openssl. I'm not sure what user chef-solo runs the command as, but as the torquebox folder belongs to the torquebox user & group, I'm assuming it needs to be that.
Here's the last bit of the error:
[2014-02-20T10:43:07+00:00] ERROR: gem_package[jruby-openssl] (torquebox::server line 85) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '137'
---- Begin output of /opt/torquebox-current/jruby/bin/jgem install jruby-openssl -q --no-rdoc --no-ri -v "0.9.4" ----
STDOUT:
STDERR: Killed
---- End output of /opt/torquebox-current/jruby/bin/jgem install jruby-openssl -q --no-rdoc --no-ri -v "0.9.4" ----
Ran /opt/torquebox-current/jruby/bin/jgem install jruby-openssl -q --no-rdoc --no-ri -v "0.9.4" returned 137
[2014-02-20T10:43:07+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.
It might be a case of just moving the gem install resource above the installation folder chown resource. Any help would be great
The text was updated successfully, but these errors were encountered:
I'm writing a wrapper cookbook for my web app (using berkshelf and vagrant—if it makes a difference), and when I run
vagrant provision
, chef-solo fails when trying to install jruby-openssl. I'm not sure what user chef-solo runs the command as, but as the torquebox folder belongs to the torquebox user & group, I'm assuming it needs to be that.Here's the last bit of the error:
It might be a case of just moving the gem install resource above the installation folder chown resource. Any help would be great
The text was updated successfully, but these errors were encountered: