Note that there are some explanatory texts on larger screens.

plurals
  1. POMoving to rbenv breaks passenger (nginx)
    primarykey
    data
    text
    <p>I moved from RVM to rbenv on my production server. I uninstalled rvm using "rvm implode" and installed rbenv, ruby 1.9.2 , rails, passenger and nginx-module. I have not modified my originlal nginx.conf apart from changing the passenger_root as follows:</p> <pre><code>1st Try: passenger_root /root/.rbenv/versions/1.9.2-p290/lib/ruby/gems/1.9.1/gems/passenger-3.0.9; passenger_ruby /root/.rbenv/versions/1.9.2-p290/bin/ruby; 2nd Try: passenger_root /root/.rbenv/shims/passenger; passenger_ruby /root/.rbenv/shims/ruby; </code></pre> <p>Now, when I try to run my application I see the following error in error.log:</p> <pre><code>[error] 1291#0: *105 open() "/home/passenger/grabber/current/public/view" failed (2: No such file or directory) </code></pre> <p>This clearly indicates that passenger has not launched and my rails app is not recognized. When I try to manually start passenger, I get the following error:</p> <pre><code> [ pid=17605 thr=70022120 file=utils.rb:176 time=2011-10-23 23:40:41.917 ]: *** Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner (libruby.so.1.9: cannot open shared object file: No such file or directory - /home/passenger/grabber/shared/bundle/ruby/1.9.1/gems/nokogiri-1.5.0/lib/nokogiri/nokogiri.so) (process 17605, thread #&lt;Thread:0x858e7d0&gt;): from /home/passenger/grabber/shared/bundle/ruby/1.9.1/gems/activesupport-3.0.9/lib/active_support/dependencies.rb:239:in `require' </code></pre> <p>I have installed nokogiri several times and I can see nokogiri in my gem list. I am not sure why moving to to rbenv has broken passenger for me. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload