ruby errors when running Passenger 4.0.48 and Ruby 2.0

531 views
Skip to first unread message

Csongor Gyuricza

unread,
Jul 31, 2014, 2:36:42 AM7/31/14
to phusion-...@googlegroups.com
Background: I'm setting up puppet 3 with passenger/apache. After running a puppet client against the master, I see the following errors in the apache logs:

/usr/share/ruby/vendor_ruby/2.0/rubygems/path_support.rb:68:in `path=': undefined method `+' for nil:NilClass (NoMethodError)
from /usr/share/ruby/vendor_ruby/2.0/rubygems/path_support.rb:30:in `initialize'
from /usr/share/ruby/vendor_ruby/2.0/rubygems.rb:357:in `new'
from /usr/share/ruby/vendor_ruby/2.0/rubygems.rb:357:in `paths'
from /usr/share/ruby/vendor_ruby/2.0/rubygems.rb:379:in `path'
from /usr/share/ruby/vendor_ruby/2.0/rubygems/specification.rb:794:in `dirs'
from /usr/share/ruby/vendor_ruby/2.0/rubygems/specification.rb:658:in `each_normal'
from /usr/share/ruby/vendor_ruby/2.0/rubygems/specification.rb:669:in `_all'
from /usr/share/ruby/vendor_ruby/2.0/rubygems/specification.rb:822:in `each'
from /usr/share/ruby/vendor_ruby/2.0/rubygems/specification.rb:864:in `find'
from /usr/share/ruby/vendor_ruby/2.0/rubygems/specification.rb:864:in `find_inactive_by_path'
from /usr/share/ruby/vendor_ruby/2.0/rubygems.rb:175:in `try_activate'
from /usr/share/ruby/vendor_ruby/2.0/rubygems/core_ext/kernel_require.rb:132:in `rescue in require'
from /usr/share/ruby/vendor_ruby/2.0/rubygems/core_ext/kernel_require.rb:144:in `require'
from <internal:abrt_prelude>:2:in `<compiled>'

Details:

[root@puppet3 ~]# gem list passenger
passenger (4.0.48)
[root@puppet3 ~]# ruby -v
ruby 2.0.0p451 (2014-02-24 revision 45167) [x86_64-linux]
[root@puppet3 ~]# [root@puppet3 ~]# yum list installed | grep httpd
httpd24.x86_64                       2.4.9-1.55.amzn1              @amzn-updates
httpd24-devel.x86_64                 2.4.9-1.55.amzn1              @amzn-updates
httpd24-tools.x86_64                 2.4.9-1.55.amzn1              @amzn-updates
[root@puppet3 ~]# 

Tinco Andringa

unread,
Aug 1, 2014, 12:03:50 PM8/1/14
to phusion-...@googlegroups.com
Hi, I see a lot of ' through your stack trace, I'm not sure if
that's related. There's no references to any passenger code though, so
I think it's something with puppet, but the html encoding makes it
really hard to decipher.

Kind regards,
Tinco
> --
> You received this message because you are subscribed to the Google Groups
> "Phusion Passenger Discussions" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to phusion-passen...@googlegroups.com.
> To post to this group, send email to phusion-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/phusion-passenger.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/phusion-passenger/ed9167fc-d264-45b3-a4e1-243a38e97e5a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Phusion | Web application deployment, scaling and monitoring solutions

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

Hongli Lai

unread,
Aug 4, 2014, 4:29:10 AM8/4/14
to phusion-passenger

I believe this is an error in the puppet client, not in passenger. The puppet authors might be able to help you further.

Sent from my Android phone.

luke....@worldprogramming.com

unread,
May 20, 2016, 5:34:59 AM5/20/16
to Phusion Passenger Discussions
In case someone else has this in the future - for me this for was caused by trying to run as a new system user without a home directory.

path_support.rb was trying to find the ENV['GEM_HOME'] and failing.  If you sudo as the user you'll find you can't gem env for example.

On linux you can use mkhomedir_helper [user] to create a home directory for the particular user you are trying to run passenger with.
Reply all
Reply to author
Forward
0 new messages