Upgrading Passenger To Latest Version

[LightBe Corp]

I believe a few weeks back it was announced that Passenger no longer needed to be compiled.  I did not read much about that since I was not having problems with Passenger.  However this morning my routes in my Rails 3.2.13 application started acting weird where sometimes the links appear properly but the page displayed is wrong.  I assume I may have done something in Passenger to cause this on my production server.  I have decided to upgrade from 4.0.10 to the latest version just to keep up with changes and possibly security patches.  When I checked the instructions in my Enterprise customer area I saw that they were a bit different than I remember when I installed 4.0.10.

I am using Passenger on a Mac Mini Server running OS X Server (Mountain Lion).  I am using RVM where I have one gemset for Ruby 1.9.3 and another one for Ruby 2.0.0.  I installed Passenger in both gemsets.  The LoadModule statements point to my 1.9.3 gemset.

I want to confirm the steps I need to take to upgrade Passenger to the latest version (4.0.20):

• gem uninstall passenger-enterprise-server-4.0.10 (each gemset)
• gem source --add https://YOUR_ORDER_REFERENCE:YOUR_P...@www.phusionpassenger.com/enterprise_gems/ (each gemset)
  
• gem install --source https://YOUR_ORDER_REFERENCE:YOUR_P...@www.phusionpassenger.com/enterprise_gems/ passenger-enterprise-server (each gemset)
• passenger-install-apache2-module (each gemset)
  
• go through steps for the RVM Helper Tool
• Update /Library/Server/Web/Config/apache2/httpd_server_app.conf with the statements pointing to my Ruby 2.0.0 gemset

The reason I am posting this is because when I checked the documentation I read some statements in the Generic installation, upgrade and downgrade method: via RubyGems section that confused me.  Do I need to do the 2nd bullet or will the 3rd bullet add to the RubyGems source file?

I also have another question.  If I want to upgrade to future versions of Passenger what will I need to do after I do this upgrade?

Any help would be appreciated.

[Hongli Lai]

If you do the second bullet point (gem source --add) then when you run
'gem install' it is not necessary to specify --source. 'gem source
--add' only has to be run once.

The instructions for upgrading are exactly the same as for installation.

> --
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.



--
Phusion | Ruby & Rails deployment, scaling and tuning solutions

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

[LightBe Corp]

Thanks.  I found this out when I decided to try them.  I was able to get 4.0.20 installed on my development server. I am able to successfully host both a 1.9.3 Rails application and a 2.0.0 Rails application with no errors.   However when I tried to install on my production server I got a lot of errors when I did the passenger-install-apache2-module command.  I have attached the output in a text file.  There are several warnings dealing with the following files that I have included below.  I saw them when I installed 4.0.20 on my development server but I did not get errors that stopped the installation.

In file included from ext/boost/libs/thread/src/pthread/thread.cpp:28:

ext/boost/libs/thread/src/pthread/./timeconv.inl:48:13: warning: unused function 'to_time' [-Wunused-function]

inline void to_time(int milliseconds, timespec& ts)

            ^

ext/boost/libs/thread/src/pthread/./timeconv.inl:86:13: warning: unused function 'to_duration' [-Wunused-function]

inline void to_duration(boost::xtime xt, int& milliseconds)

            ^

ext/boost/libs/thread/src/pthread/./timeconv.inl:108:13: warning: unused function 'to_microduration' [-Wunused-function]

inline void to_microduration(boost::xtime xt, int& microseconds)

I also noticed that when I did the uninstall of 4.0.10 the folders were still in my gemset.  Do I need to physically remove them?  I can confirm that I am running 4.0.20.

On Monday, October 14, 2013 12:26:10 PM UTC-5, Hongli Lai wrote:

If you do the second bullet point (gem source --add) then when you run
'gem install' it is not necessary to specify --source. 'gem source
--add' only has to be run once.

The instructions for upgrading are exactly the same as for installation.

On Mon, Oct 14, 2013 at 6:40 PM, LightBe Corp <iktu...@mac.com> wrote:
> I believe a few weeks back it was announced that Passenger no longer needed
> to be compiled.  I did not read much about that since I was not having
> problems with Passenger.  However this morning my routes in my Rails 3.2.13
> application started acting weird where sometimes the links appear properly
> but the page displayed is wrong.  I assume I may have done something in
> Passenger to cause this on my production server.  I have decided to upgrade
> from 4.0.10 to the latest version just to keep up with changes and possibly
> security patches.  When I checked the instructions in my Enterprise customer
> area I saw that they were a bit different than I remember when I installed
> 4.0.10.
>
> I am using Passenger on a Mac Mini Server running OS X Server (Mountain
> Lion).  I am using RVM where I have one gemset for Ruby 1.9.3 and another
> one for Ruby 2.0.0.  I installed Passenger in both gemsets.  The LoadModule
> statements point to my 1.9.3 gemset.
>
> I want to confirm the steps I need to take to upgrade Passenger to the
> latest version (4.0.20):
>
> gem uninstall passenger-enterprise-server-4.0.10 (each gemset)
> gem source --add

> https://YOUR_ORDER_REFERENCE:YOUR_PASSWORD@www.phusionpassenger.com/enterprise_gems/

> (each gemset)
> gem install --source

> https://YOUR_ORDER_REFERENCE:YOUR_PASSWORD@www.phusionpassenger.com/enterprise_gems/

[Hongli Lai]

On Mon, Oct 14, 2013 at 7:33 PM, LightBe Corp <iktu...@mac.com> wrote:
> Thanks. I found this out when I decided to try them. I was able to get
> 4.0.20 installed on my development server. I am able to successfully host
> both a 1.9.3 Rails application and a 2.0.0 Rails application with no errors.
> However when I tried to install on my production server I got a lot of
> errors when I did the passenger-install-apache2-module command. I have
> attached the output in a text file. There are several warnings dealing with
> the following files that I have included below. I saw them when I installed
> 4.0.20 on my development server but I did not get errors that stopped the
> installation.

Could you attach the file
/Users/serverremote1/.rvm/gems/ruby-2.0.0-p247@LightBeCorp_Rails4Ruby2/gems/passenger-enterprise-server-4.0.20/buildout/libev/config.log?

> I also noticed that when I did the uninstall of 4.0.10 the folders were
> still in my gemset. Do I need to physically remove them? I can confirm
> that I am running 4.0.20.

It's not necessary to physically remove them.

[LightBe Corp]

Here it is.

[Hongli Lai]

It looks like the compilation problem is caused by different parts of
the build system selecting different default compilers. We'll fix this
in the next release. In the mean time you can work around this problem
by forcing a single compiler by setting these environment variables:

export CC=gcc
export CXX=g++

> --
> 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.
> For more options, visit https://groups.google.com/groups/opt_out.

[LightBe Corp]

I have not done this before.  What commands do I need to execute to set the variables and where?   

Thanks so much for your kind help.  I may post this in Stack Overflow for others if I find similar problems.  You all have great customer service.

[LightBe Corp]

I did a web search on how to and added the statements to ~/.MacOSX/environment.plist and rebooted my servers.  Unfortunately I still get the same error when I try to execute rvmsudo passenger-install-apache2-module on my production server. I also see the same warning messages I mentioned in a previous response. I have attached a copy of the output and the config.log file.

[Tinco Andringa]

Hi,

Our apologies for the late response. The easiest way to make sure
these environment variables are set is to execute the export commands
right before you compile passenger. Like so:

$ export CC=gcc
$ export CXX=g++
$ rvmsudo passenger-install-apache2-module

If Hongli was correct this should fix your issue with compiling. Note
that this is only a workaround and in the next release it will no
longer be necessary to take this steps.

Hope this helps.

Kind regards,
Tinco Andringa

[Tinco Andringa]

Woops, I forgot that rvmsudo clears your environment variables, the
correct sequence would be:

$ export CC=gcc
$ export CXX=g++

$ rvmsudo -E passenger-install-apache2-module

Kind regards,
Tinco Andringa

[LightBe Corp]

I was successful.  Passenger is up and running on both our servers.  Thanks.  Hopefully this will clear up the problems we were having with our Rails application.

I have another question.  When you release a new version of Passenger how would we implement it? Before we would download the file from your website and install the gem.  Would we just do another rvmsudo gem install passenger-enterprise-server in each gemset?

[Hongli Lai]

On Tue, Oct 15, 2013 at 6:01 PM, LightBe Corp <iktu...@mac.com> wrote:
> I was successful. Passenger is up and running on both our servers. Thanks.
> Hopefully this will clear up the problems we were having with our Rails
> application.
>
> I have another question. When you release a new version of Passenger how
> would we implement it? Before we would download the file from your website
> and install the gem. Would we just do another rvmsudo gem install
> passenger-enterprise-server in each gemset?

That is correct. Now that you have our gem server in the gem source
list, you can just do 'gem install passenger-enterprise-server'
instead of downloading the gem file and running 'gem install
downloaded-file.gem'. You still have to run
passenger-install-apache2-module.