Phusion white papers Phusion overview

Phusion Blog

Phusion Passenger 3.0.0 public beta 2 released

By Hongli Lai on September 17th, 2010

Thanks to all the users who have provided constructive feedback! This release fixes all newly reported issues so far.

Phusion Passenger Standalone now correctly handles paths with spaces in them
Beta 1 would error out with a weird message.
Fixed some RVM support issues
If you’re using RVM and you had problems with beta 1, try this version. Thanks to Wayne for helping out!
Improved watchdog startup error checking
If the watchdog crashes during startup then the reason wasn’t always obvious. We’ve improved the startup error checking code so that more error information can be collected.
Fixed Phusion Passenger Standalone binary compatibility string generation
The binary compatibility string is generated from many components, including part of the output of ‘uname -p’. It turns out that on some systems that command outputs in an unexpected format.
Fixed curl error detection
Curl is used to download things when wget is not available. Beta 1 did not correctly recognize cases in which curl exit because of an HTTP 404 error.
Fixed PassengerMinInstances default value on Apache
It’s supposed to be 1, but in beta 1 it was accidentally still 0.
Fixed support for older Apache 2 versions
Beta 1 used API calls which are only available in newer versions.
Fixed various compilation warnings
Including warnings on CentOS 5 and Ubuntu 10.04.

Installation/upgrade

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:

passenger-install-apache2-module
passenger-install-nginx-module

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

  • It’s amazing how quick you are 🙂

  • Hello,

    Clean setup, Snow Leopard, no ~/.passenger directory exist. RVM with 1.9.2 and passenger pre2 gem, fails to compile standalone mode:

    http://gist.github.com/584637

    Where should I report this instead the blog?

    Thank you.

  • To add to previous comment, seems that passenger is trying to find the Ruby installation inside the gemset:

    /Users/luis/.rvm/wrappers/ruby-1.9.2-p0@pass3/ruby /Users/luis/.rvm/gems/ruby-1.9.2-p0@pass3/bin/rake package:filelist –silent

    Where Ruby is actually here:

    $ which ruby
    /Users/luis/.rvm/rubies/ruby-1.9.2-p0/bin/ruby

    HTH

  • I’m also having issues – beta 1 worked perfectly but can’t install beta 2:

    http://gist.github.com/584698

    $ which ruby
    /Users/caffo/.rvm/rubies/ruby-1.8.7-p249/bin/ruby

    Thanks

  • @Luis Lavena: I’ll contact Wayne about this. ~/.rvm/wrappers is a fairly recent RVM feature and we depend on it. It would appear that the RVM upgrade path is non-obvious at this time.

    @Rodrigo Franco: Can you post the outputs of the following commands?

    ls /Users/caffo/.rvm/wrappers
    ruby -e 'puts ENV["GEM_HOME"]'
  • Mark

    I’ve always updated rvm with:
    rvm update –head
    rvm reload

  • Mark

    should be two dashes before head, stupid blog comment auto formatting. 😛

  • Yeah but it appears that the wrapper scripts don’t get updated when you run ‘rvm update –head’.

  • Can’t use it. Same error on beta1. and beta2.

    http://gist.github.com/584896

    Mo matter if I try to compile nginx module or the standalone version it stops with error (see above).
    I tried with rvm –head version, on ruby 1.8.7 and ruby 1.9.2, with default nginx and with –nginx-version 0.8.50.

  • @kfl62: should now be fixed in Phusion Passenger git commit 309b427.

  • Wow fast response 🙂

    I clone it now

  • Excellent. Now that paths with spaces work, standalone is working perfectly, and may just become my main development server! 😀

  • Good news!

    I can’t build the gem:

    rake aborted!
    could not find template “./doc/template/horo”

    but building with ./bin/passenger start, works 🙂
    So lets start testing.

    Thx

  • Pingback: Link dump for September 17th | The Queue Blog()

  • On Ubuntu I fail with

    Curl development headers with SSL support… not found

    even though libcurl4-openssl-dev is installed.

    Adding -lidn to the gcc command fixes passenger-curl-check.c compile. Not sure if this is something wrong with my environment or something that needs to be fixed in passenger.

    Details are here http://gist.github.com/587853

  • ignore this if it is a duplicate. I swear I posted this comment an hour ago.

    Having issues getting nginx to compile on Ubuntu with the passenger

    * Curl development headers with SSL support… not found

    gcc is not including -lidn

    Details.
    http://gist.github.com/587853

  • do you know http://www.cherokee-project.com/?
    know how I can use the mod_rails/passenger with the Cherokee?

  • Herminio, we have no plans to support Cherokee at this time since there doesn’t appear to be a lot of user demand for it. Of course we are open for discussing any sponsoring possibilities.

  • Here goes guys:

    1 – I don’t have a wrappers file

    ls /Users/caffo/.rvm/wrappers
    ls: /Users/caffo/.rvm/wrappers: No such file or directory

    2 – My gems home is set to:

    ruby -e ‘puts ENV[“GEM_HOME”]’
    /Users/caffo/.rvm/gems/ruby-1.8.7-p249%global

    Thanks!

  • @Tony: maybe you want to look at http://code.google.com/p/phusion-passenger/issues/detail?id=533

    @Rodrigo: use beta 3.

  • Simon de Boer

    Porting over a complex application from 2.3.8 to 3.0 – using Passenger 3.0.0-pre3…

    Receiving: Could not find rack-test-0.5.5 in any of the sources (Bundler::GemNotFound)

    I don’t require it, and I assume it is a dependency of Passenger. I installed the gem and it can be found from irb or rails console. If I add it to the local Gemfile and do `bundle install` it reports it can find it as well.

  • Simon de Boer

    Follow up…Running it standalone gave a different error.

    A custom library, in the lib directory, that was no longer automatically available, was being include’d into ApplicationController. Once this was fixed the rack-test problem went away.

  • @Simon: Phusion Passenger doesn’t depend on rack-test.

  • Phil Thompson

    I get an error on Ubuntu 10.04 and rvm (latest):

    cd: 1: can’t cd to ext/libev

    I guessed it was a permissions issue and did:

    rvmsudo passenger start

    instead and this got things going.

    Just thought I’d mention it.

    This is awesome BTW!

  • @Tony: maybe you want to look at http://code.google.com/p/phusion-passenger/issues/detail?id=533 @Rodrigo: use beta 3.

  • Bhupendra

    issue while install curl on ubantu. I followed step as…

    $ gem install passenger

    $ passenger-install-apache2-module

    got error as follows

    * GNU C++ compiler… found at /usr/bin/g++
    * Curl development headers with SSL support… not found
    * OpenSSL development headers… found
    * Zlib development headers… found
    * Ruby development headers… found
    * OpenSSL support for Ruby… found
    * RubyGems… found
    * Rake… found at /var/lib/gems/1.8/bin/rake
    * rack… found
    * Apache 2… found at /usr/sbin/apache2
    * Apache 2 development headers… found at /usr/bin/apxs2
    * Apache Portable Runtime (APR) development headers… found at /usr/bin/apr-1-config
    * Apache Portable Runtime Utility (APU) development headers… found at /usr/bin/apu-1-config

    Some required software is not installed.

    —————————————–
    $ apt-get install libcurl4-openssl-dev

    got error as follows
    ————————————–
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    The following extra packages will be installed:
    libcurl3 libidn11-dev
    Suggested packages:
    libcurl3-dbg
    The following NEW packages will be installed
    libcurl4-openssl-dev libidn11-dev
    The following packages will be upgraded:
    libcurl3
    1 upgraded, 2 newly installed, 0 to remove and 346 not upgraded.
    Need to get 1700kB of archives.
    After this operation, 3293kB of additional disk space will be used.
    Do you want to continue [Y/n]? y
    WARNING: The following packages cannot be authenticated!
    libcurl3 libidn11-dev libcurl4-openssl-dev
    Install these packages without verification [y/N]? y
    Err http://in.archive.ubuntu.com intrepid-updates/main libcurl3 7.18.2-1ubuntu4.4
    404 Not Found
    Err http://security.ubuntu.com intrepid-security/main libcurl3 7.18.2-1ubuntu4.4
    404 Not Found [IP: 91.189.92.166 80]
    Err http://in.archive.ubuntu.com intrepid/main libidn11-dev 1.8+20080606-1
    404 Not Found
    Err http://in.archive.ubuntu.com intrepid-updates/main libcurl4-openssl-dev 7.18.2-1ubuntu4.4
    404 Not Found
    Err http://security.ubuntu.com intrepid-security/main libcurl4-openssl-dev 7.18.2-1ubuntu4.4
    404 Not Found [IP: 91.189.92.166 80]
    Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/c/curl/libcurl3_7.18.2-1ubuntu4.4_i386.deb 404 Not Found [IP: 91.189.92.166 80]
    Failed to fetch http://in.archive.ubuntu.com/ubuntu/pool/main/libi/libidn/libidn11-dev_1.8+20080606-1_i386.deb 404 Not Found
    Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/c/curl/libcurl4-openssl-dev_7.18.2-1ubuntu4.4_i386.deb 404 Not Found [IP: 91.189.92.166 80]
    E: Unable to fetch some archives, maybe run apt-get update or try with –fix-missing?

  • james

    This bug is still not fixed in 3.0.4. I’m compiling nginx module with nginx 0.8.54. on xubuntu maverick. even after apt-get install libcurl4-openssl-dev. I’m still geting error message

    Curl development headers with SSL support… not found

  • I had a similar issue with this and could not figure out why the problem was. I happen to be logged in as root one day and needed to start passenger. Was too lazy to ‘exit’ and figured that it wouldn’t work anyways.

    However, I ran ‘passenger start’ as root and it worked! I tried again as my normal user and got the same error codes. For whatever reason, it wanted me to be root to find the two culprits.

  • Max

    Trying to upgrade passenger on MAC OS 10.5.8 to 3.0.5 — getting

    Curl development headers with SSL support… not found

    Tried installing curl (–with-ssl) and when that failed, tried installing curl ( and –with-ssl=/System/Library/OpenSSL) and finally with ( ./configure –prefix=/usr/bin/ –with-ssl=/System/Library/OpenSSL)

    No joy — is this still a bug? Does anyone know if it’s possible to upgrade passenger on MAC OS 10.5.8 server without ports?

    Thanks