Phusion white papers Phusion overview

Phusion Blog

Phusion Passenger 3.0.0 public beta 3 released

By Hongli Lai on September 20th, 2010

What’s new

More RVM issues fixed
A lot of people who happen to use RVM have reported various problems. Some of the symptoms include:

  • The spawn server crashes during startup.
  • Phusion Passenger Standalone prints ‘command not found’ errors.

It turned out that these problems occur when one has an older RVM version installed. Phusion Passenger depends on features provided by relatively new RVM versions. We’ve added sanity checks in Phusion Passenger so that it warns you if it detects an old RVM installation.

You can upgrade your RVM installation by running these commands:

rvm update --head
rvm reload
rvm repair all

We’ve also fixed support for system-wide RVM installs.

Aggressively checks for permissions
Many problems that people report on the Phusion Passenger discussion board are actually caused by wrong permissions set on the application files or on one of the parent directories. We’ve added aggressive permission checking code in Phusion Passenger. If any permissions are wrong then it will tell the user exactly which directory has wrong permissions and how to fix it. This should make Phusion Passenger a lot more fail-proof than before.
Fixed some more compilation problems
These problems occur on some systems but not on others.
Fixed passenger-status crash
When passenger-status tries to tell the user that it needs to be run as root, it used to crash instead because of a typo.
Phusion Passenger Standalone checks for GNU make on FreeBSD
Phusion Passenger Standalone depends on the GNU version of make in order to be able to show a compilation progress bar.


First install the latest Phusion Passenger gem:

gem install passenger --pre

(Or you can download the tarball.)

If you want to install or upgrade the Apache or Nginx version, then run the installer as you’re used to:


At the end the installer will tell you to paste a configuration snippet. If you’re upgrading then replace the old snippet with the new one.

If you want to run Phusion Passenger Standalone, then run:

cd /path-to-your-app
passenger start

No special upgrade instructions needed.

The documentation

Users guide for Apache
Users guide for Nginx
Users guide for Standalone

  • When Passenger will be able to work with more than one Ruby version? RubyRoot option should be set per vhost, not only once and global for all vhosts

  • I was going to comment and then noticed that hipertracker wrote exactly what I wanted to know (except I’d refer to PassengerRuby). This really is important to people.

  • These comments are exactly what I was looking for.
    It would be awesome if PassengerRuby could be set per vhost 🙂

  • Gerhard

    When I try to set up Passenger 3.0.0.pre3 on a system-wide rvm 1.0.11 setup, it wrongly assumes that it should load the rvm environment from ~user/.rvm. The rvm environment is set up in /usr/local/rvm. Cheers!

  • @Gerhard: I think that’s an RVM issue, not a Phusion Passenger issue. What’s the value of your PassengerRuby directive?

  • Gerhard

    Sorry, I wasn’t too clear, I am using passenger standalone, starting it with passenger start.

  • What do you see when you run this?

    ruby -rubygems -e "require 'phusion_passenger/platform_info/ruby'; puts PhusionPassenger::PlatformInfo.ruby_command"
  • Tob

    When do you anticipate the sharp release of 3.0.0? Thanks

  • Gerhard

    Hongli, this is what I get back


  • Can you paste the contents of /usr/local/rvm/wrappers/ruby-1.9.2-p0/ruby?

  • Gerhard

    An update –head & repair all fixed it. Now on rvm 1.0.12. Cheers Hongli!