Nginx – How to fix NginX/Phusion/Passenger “zsh:1: no such file or directory: passenger/buildout/agents/SpawnPreparer”

nginxphusion-passenger

Hopefully this is the correct site to ask this question.

I've got a webservice I'm attempting to set up using NginX with Phusion Passenger riding a Ruby Sinatra application. The problem is that when I try to start the server and test the site, I get the following error:

zsh:1: no such file or directory: passenger/buildout/agents/SpawnPreparer

Now, I've been able to determine that SpawnPreparer is calling zsh, although, I'm not sure why. I don't even use zsh and I wasn't using it when I built the server. Nevertheless, what I'd like to know is if it's possible to configure passenger in the nginx.conf to use a different shell with which to spawn its processes? If so, how?

This is Phusion 4.0.14

Thanks!

Best Answer

When Phusion Passenger spawns an application, it does so by invoking the command $SHELL -lc '/path-to-passenger-root/buildout/agents/SpawnPreparer /path-to-passenger-root/helper-scripts/rack-loader.rb <SOME ARGUMENTS>'. It's described here: https://github.com/phusion/passenger/wiki/Debugging-application-startup-problems#the-spawning-process-explained. Here, $SHELL is the user's shell, as configured in the OS's user database (/etc/passwd). In your case, your user is setup with zsh as its shell. This is probably your OS's default setting.

Your error message indicates that it cannot execute the file passenger/buildout/agents/SpawnPreparer. In other words, Phusion Passenger thinks that /path-to-passenger equals passenger. This probably means that you set the incorrect value for the passenger_root directive, which dictates the proper value of /path-to-passenger.

Related Solutions

Nginx – How to only serve https using passenger 2.2.9, nginx 0.7.65, and sinatra 0.94

if you type in http://server/ the browser sends plain text request to the server on port 80. whereas if you type in https://server/ it'll send encrypted request to port 443. what you're doing is you sending plain text to https, so webserver expects encrypted, but gets plain.

it'd work if you did https://server:80/, so webrowser knows it needs to encrypt, but sends to 80. i doub't you can expect that from users.

what you want to is, accept unencrypted traffic on 80, and just http redirect all requests to 443. in nginx:

server {
  listen server_ip:80;
  server_name server_name;
  location / {
    rewrite ^/(.*) https://server_name permanent;
  }
}

Ubuntu – Apache Passenger can’t find gem

Check your Passenger module configuration files. In my case

content of /etc/apache2/mods-enabled/passenger.load:

LoadModule passenger_module /usr/lib/ruby/gems/1.8/gems/passenger2.2.5/ext/apache2/mod_passenger.so

content of /etc/apache2/mods-enabled/passenger.conf:

<IfModule mod_passenger.c>
  PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-2.2.5
  PassengerRuby /usr/local/bin/ruby
</IfModule>

PassengerRuby is telling module what ruby interpreter to use.

Best Answer

Related Solutions

Nginx – How to only serve https using passenger 2.2.9, nginx 0.7.65, and sinatra 0.94

Ubuntu – Apache Passenger can’t find gem

Related Topic