Ruby 1.9.1 p376 and Passenger

[jzajpt]

Hi,

I've been waiting for the new Ruby 1.9 hoping that it would fix error
in tempfile library mentioned here http://groups.google.com/group/phusion-passenger/msg/9e161c9623b1c75b.
I've upgraded to latest ruby 1.9.1 p376 today only to find out that
Passenger still breaks down on any POST request:

/!\ FAILSAFE /!\ 2009-12-07 17:16:58 +0100
Status: 500 Internal Server Error
closed stream
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/vendor/
rack-1.0.0-git/lib/rack/rewindable_input.rb:86:in `make_rewindable'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/vendor/
rack-1.0.0-git/lib/rack/rewindable_input.rb:26:in `read'
/Users/jzajpt/Code/active/billapp/vendor/gems/rack-1.0.1/lib/rack/
request.rb:134:in `POST'
/Users/jzajpt/Code/active/billapp/vendor/gems/rack-1.0.1/lib/rack/
methodoverride.rb:15:in `call'
/Users/jzajpt/Code/active/billapp/vendor/rails/actionpack/lib/
action_controller/params_parser.rb:15:in `call'
/Users/jzajpt/Code/active/billapp/vendor/rails/actionpack/lib/
action_controller/session/cookie_store.rb:93:in `call'
/Users/jzajpt/Code/active/billapp/vendor/rails/actionpack/lib/
action_controller/failsafe.rb:26:in `call'
/Users/jzajpt/Code/active/billapp/vendor/gems/rack-1.0.1/lib/rack/
lock.rb:11:in `block in call'
<internal:prelude>:8:in `synchronize'
/Users/jzajpt/Code/active/billapp/vendor/gems/rack-1.0.1/lib/rack/
lock.rb:11:in `call'
/Users/jzajpt/Code/active/billapp/vendor/rails/actionpack/lib/
action_controller/dispatcher.rb:114:in `block in call'
/Users/jzajpt/Code/active/billapp/vendor/rails/actionpack/lib/
action_controller/reloader.rb:34:in `run'
/Users/jzajpt/Code/active/billapp/vendor/rails/actionpack/lib/
action_controller/dispatcher.rb:108:in `call'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/rack/request_handler.rb:95:in `process_request'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/abstract_request_handler.rb:207:in `main_loop'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/railz/application_spawner.rb:374:in
`start_request_handler'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/railz/application_spawner.rb:332:in `block in
handle_spawn_application'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/utils.rb:184:in `safe_fork'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/railz/application_spawner.rb:330:in
`handle_spawn_application'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/abstract_server.rb:352:in `main_loop'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/abstract_server.rb:196:in `start_synchronously'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/abstract_server.rb:163:in `start'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/railz/application_spawner.rb:209:in `start'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/spawn_manager.rb:262:in `block (2 levels) in
spawn_rails_application'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/spawn_manager.rb:256:in `block in
spawn_rails_application'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/abstract_server_collection.rb:80:in `block in
synchronize'
<internal:prelude>:8:in `synchronize'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/spawn_manager.rb:255:in `spawn_rails_application'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/spawn_manager.rb:154:in `spawn_application'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/spawn_manager.rb:287:in `handle_spawn_application'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/abstract_server.rb:352:in `main_loop'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/
phusion_passenger/abstract_server.rb:196:in `start_synchronously'
/opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/bin/
passenger-spawn-server:61:in `<main>'

I don't want to use 1.9.1p129 anymore - which works fine - as it
contains some vulnerabilities. Any help would be appreciated.

[Anuj Dutta]

2009/12/7 jzajpt <jza...@gmail.com>

--

You received this message because you are subscribed to the Google Groups "Phusion Passenger Discussions" group.
To post to this group, send email to phusion-...@googlegroups.com.
To unsubscribe from this group, send email to phusion-passen...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/phusion-passenger?hl=en.

Have a look at this:IO Error

It seems to have been fixed in 1.9.2dev. I have not tried it though.

I did not know it works fine with Ruby 1.9.1p129. I was frustrated and just went back to Ruby 1.8.7.

Anuj

--
Anuj DUTTA

[chris]

I am getting the same thing. How can a person get passenger to use
ruby 1.8.7 rather than the 1.9.x that is auto refers to. I never
actually installed Ruby 1.9 myself looks like Passenger bundles it up.

nginx.conf snippet:
===================
passenger_root /usr/lib/ruby/gems/1.9.1/gems/passenger-2.2.7;
passenger_ruby /usr/bin/ruby;

===================
[chris@staging]$ ruby --version
ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux]

> > phusion-passen...@googlegroups.com<phusion-passenger%2Bunsubscr i...@googlegroups.com>
> > .

> > For more options, visit this group at
> >http://groups.google.com/group/phusion-passenger?hl=en.
>
> Have a look at this:IO

> Error<http://groups.google.com/group/phusion-passenger/browse_thread/thread...>

[Anuj Dutta]

2009/12/10 chris <olsen...@gmail.com>

I am getting the same thing. How can a person get passenger to use
ruby 1.8.7 rather than the 1.9.x that is auto refers to. I never
actually installed Ruby 1.9 myself looks like Passenger bundles it up.

nginx.conf snippet:
===================
passenger_root /usr/lib/ruby/gems/1.9.1/gems/passenger-2.2.7;
passenger_ruby /usr/bin/ruby;

Did you install ruby 1.8.7 yourself? Then check in /usr/local/bin there might be a ruby executable which points to ruby 1.8.7 and /usr/bin/ruby points at Ruby 1.9. And when you run ruby -v on the shell it goes and looks in /usr/local/bin first and it finds a ruby there and it shows you that version which id correct. To fix it, just do this:

passenger_ruby /usr/local/bin/ruby;


Having said all this, I would suggest you look at: http://www.taylorluk.com/articles/2009/08/12/ruby-19-and-passenger

Hope it helps.

Anuj (andHapp)

 

To unsubscribe from this group, send email to phusion-passen...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/phusion-passenger?hl=en.

--
Anuj DUTTA

[chris]

You were right in regards to the location of ruby 1.8.7.
Unfortunately, after making the change I get a failure simular to the
ones posted at http://code.google.com/p/phusion-passenger/issues/detail?id=96



On Dec 10, 12:16 am, Anuj Dutta <dutta.a...@googlemail.com> wrote:
> 2009/12/10 chris <olsen.ch...@gmail.com>

> > > > phusion-passen...@googlegroups.com<phusion-passenger%2Bunsubscr i...@googlegroups.com><phusion-passenger%2Bunsubscr

> > i...@googlegroups.com>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/phusion-passenger?hl=en.
>
> > > Have a look at this:IO
> > > Error<
> >http://groups.google.com/group/phusion-passenger/browse_thread/thread...>
>
> > > It seems to have been fixed in 1.9.2dev. I have not tried it though.
>
> > > I did not know it works fine with Ruby 1.9.1p129. I was frustrated and
> > just
> > > went back to Ruby 1.8.7.
>
> > > Anuj
>
> > > --
> > > Anuj DUTTA
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Phusion Passenger Discussions" group.
> > To post to this group, send email to phusion-...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > phusion-passen...@googlegroups.com<phusion-passenger%2Bunsubscr i...@googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/phusion-passenger?hl=en.
>

> --
> Anuj DUTTA

[Anuj Dutta]

2009/12/10 chris <olsen...@gmail.com>

You were right in regards to the location of ruby 1.8.7.
Unfortunately, after making the change I get a failure simular to the
ones posted at http://code.google.com/p/phusion-passenger/issues/detail?id=96

ahh...you see I am using nginx. Well, I am not sure how urgent this is but you could give nginx a try as well and see if that works. I will try apache on my server and see if I have that problem.

Anuj

 

To unsubscribe from this group, send email to phusion-passen...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/phusion-passenger?hl=en.

--
Anuj DUTTA

[chris]

Oops, that was the wrong link.

This is the error that I am now getting although I am not using ruby-
enterprise.
http://code.google.com/p/phusion-passenger/issues/detail?id=96

On Dec 10, 9:45 am, chris <olsen.ch...@gmail.com> wrote:
> You were right in regards to the location of ruby 1.8.7.
> Unfortunately, after making the change I get a failure simular to the

> ones posted athttp://code.google.com/p/phusion-passenger/issues/detail?id=96

[chris]

I guess that was the right link.

I am using nginx as well. It was just the error message that I am
getting that is simular.

If I look at the nginx error.log file it claims to have problems
requiring rubygems on line 16 of /usr/lib/ruby/gems/1.9.1/gems/
passenger-2.2.7/lib/phusion_passenger/utils.rb.

If I open irb and type "require 'rubygems'" I do get an error of
"LoadError: no such file to load -- rubygems"

Now at the prompt rubygems show as being there as v1.3.5 with gem -v

On Dec 10, 9:58 am, chris <olsen.ch...@gmail.com> wrote:
> Oops, that was the wrong link.
>
> This is the error that I am now getting although I am not using ruby-

> enterprise.http://code.google.com/p/phusion-passenger/issues/detail?id=96

[Anuj Dutta]

2009/12/10 chris <olsen...@gmail.com>

Oops, that was the wrong link.

This is the error that I am now getting although I am not using ruby-
enterprise.

http://code.google.com/p/phusion-passenger/issues/detail?id=96

You posted the same link. :o)

Anuj

 

To unsubscribe from this group, send email to phusion-passen...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/phusion-passenger?hl=en.

--
Anuj DUTTA

[Anuj Dutta]

2009/12/10 chris <olsen...@gmail.com>

I guess that was the right link.

I am using nginx as well.  It was just the error message that I am
getting that is simular.

If I look at the nginx error.log file it claims to have problems
requiring rubygems on line 16 of /usr/lib/ruby/gems/1.9.1/gems/
passenger-2.2.7/lib/phusion_passenger/utils.rb.

If I open irb and type "require 'rubygems'" I do get an error of
"LoadError: no such file to load -- rubygems"

Now at the prompt rubygems show as being there as v1.3.5 with gem -v

Ofcourse that is the problem. So you do not have rubygems for ruby 1.8.7. You will have to reinstall rubygems for it. I think you just download the tar file. Untar it. and just run ruby setup.rb file in the directory that gets created when you run untar. And that should fix your problem. Rubygems you have on your system is hooked up to Ruby 1.9 and since you have moved to Ruby 1.8.7 you need to reinstall it....that makes sense?

Anuj

 

To unsubscribe from this group, send email to phusion-passen...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/phusion-passenger?hl=en.

--
Anuj DUTTA

[chris]

It does, although I am a little confused to why this happened. The
only reference to the ruby 1.9 libs was in the nginx.conf file. Since
`ruby -v` would always show 1.8.7 would that not have been the version
that I was running for everything else ie installing gems, irb?

On Dec 10, 10:14 am, Anuj Dutta <dutta.a...@googlemail.com> wrote:
> 2009/12/10 chris <olsen.ch...@gmail.com>
>

> > > > > > > It seems to have been fixed in 1.9.2dev. I...
>
> read more »

[chris]

That was it. I am not sure how ruby1.9 overtook 1.8, but it did.

Thanks for the help Anuj.

On Dec 10, 10:14 am, Anuj Dutta <dutta.a...@googlemail.com> wrote:
> 2009/12/10 chris <olsen.ch...@gmail.com>
>

> > > > > > > It seems to have been fixed in 1.9.2dev. I...
>
> read more »

[Anuj Dutta]

2009/12/10 chris <olsen...@gmail.com>

It does, although I am a little confused to why this happened.  The
only reference to the ruby 1.9 libs was in the nginx.conf file.  Since
`ruby -v` would always show 1.8.7 would that not have been the version
that I was running for everything else ie installing gems, irb?

So is it working now?

Passenger -> only knows about ruby through the passenger_ruby version which was pointed at /usr/local/ruby which is ruby 1.9. Just to confirm do this: /usr/bin/ruby -v and it would show version 1.9.

Shell -> In the shell, when you run ruby -v it looks through the directories in PATH for this executable. It looks into user /usr/local/bin and finds a ruby executable and runs that. So, when you run ruby -v in the shell you see ruby 1.8.7. Had you not installed this version this would have shown you ruby 1.9 because it would have found no executable named 'ruby' in /usr/loca/bin and carried on looking for it and eventually find it in /usr/bin/.

Every version of ruby has its own copy of rubygems. If you do ls -l /usr/local/lib/ruby/site_ruby you will see two different directories for 1.8 and 1.9. Each of these directories has a copy of its rubygems, therefore you had to install it yourself for ruby 1.8.7. Since, you had no rubygems for ruby 1.8.7, when you ran irb it gave you the error messages because it was an interactive session for ruby 1.8.7.

You must be wondering...ok that's fine but how the hell was gem command working when I had no rubygems installed. It should have given you some error becaue ruby 1.8.7 had no rubygems installed but strangely it was working fine. Well, gem is bascially an executable script. When you run an executable script in linux it looks for it in the directories in its PATH. So, it started its search and since you had no gem installed for ruby 1.8.7 ( I mean there was no gem executable in /usr/local/bin) it carried on and found the one in /usr/bin which is linked to the rubygems for version 1.9. I am guessing the reason you are confused is because you expected that intallation of ruby 1.8.7 would overwrite executables for ruby 1.9 but instead it creates fresh executables in /usr/local/bin.

Well I am not the sharpest tool in the toolbox, when it comes to explaning things. I hope it helps.

Anuj

 

To unsubscribe from this group, send email to phusion-passen...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/phusion-passenger?hl=en.

--
Anuj DUTTA

[MilesTogoe]

On 12/10/2009 10:08 AM, chris wrote:
> I guess that was the right link.
>
> I am using nginx as well. It was just the error message that I am
> getting that is simular.
>
> If I look at the nginx error.log file it claims to have problems
> requiring rubygems on line 16 of /usr/lib/ruby/gems/1.9.1/gems/
> passenger-2.2.7/lib/phusion_passenger/utils.rb.
>
> If I open irb and type "require 'rubygems'" I do get an error of
> "LoadError: no such file to load -- rubygems"
>
> Now at the prompt rubygems show as being there as v1.3.5 with gem -v
>

fwiw - have been running passenger with 1.9.1 p-243 with no problem
(have just downloaded the new p376 and will try shortly) but..

1) with 1.9.1 gems are built in so you don't need "require 'rubygems' "
but having it shouldn't give errors either

2) since you're getting gem errors odds are you might have messed up
your gems switching between versions. Personally I would clean out all
the versions and reinstall 1.9.1 - then when you install gems they will
be placed correctly under 1.9.1

3) we had problems with passenger + nginx due to the permission
requirements of nginx - obviously others have worked around it but we
had trouble so we went back to Apache and had it loaded and running in 5
mins.

4) going back to 1.8.7 is simply going backwards - 1.9.1 is the current
"official" version (and offers lots of improvements) . I understand
those who are already with 1.8.x not wanting to upgrade (ain't broke,
don't fix) but if you're starting, you really should be in the 1.9.1
series (a few old gems might hiccup but can usually be quickly fixed)

> To unsubscribe from this group, send email to phusion-passen...@googlegroups.com.

[Anuj Dutta]

That's absolutely right. I had the same intentions but I had a deadline and the site had to go up so a moment of weakness took over. So, it works fine with Apache. I will try it out as well. 

Thanks a lot.

Anuj

2009/12/11 MilesTogoe <miles...@gmail.com>

--
Anuj DUTTA

[chris]

That sounded like a pretty good explanation to me. Everything is
working now. Now that I think about it I installed Ruby via pacman
which is where 1.9 came from. This is all good to know for when I
setup up the production server.

> >  /opt/local/lib/ruby1.9/gems/1.9.1/gems/passenger-2.2.7/lib/...
>
> read more »

[Anuj Dutta]

2009/12/11 chris <olsen...@gmail.com>

That sounded like a pretty good explanation to me.  Everything is
working now.  Now that I think about it I installed Ruby via pacman
which is where 1.9 came from.  This is all good to know for when I
setup up the production server.

I am glad it helped you in some way. Consider Ruby Version Manager if you would like to play around with multiple versions of ruby on your development machine.

Anuj

 

>
> read more »

--

You received this message because you are subscribed to the Google Groups "Phusion Passenger Discussions" group.
To post to this group, send email to phusion-...@googlegroups.com.
To unsubscribe from this group, send email to phusion-passen...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/phusion-passenger?hl=en.

--
Anuj DUTTA

[chris]

Miles,

> 1) with 1.9.1 gems are built in so you don't need "require 'rubygems' " but having it shouldn't give errors either

This only happened once I told passenger to use Ruby 1.8

> 2) since you're getting gem errors odds are you might have messed up your gems switching between versions. Personally I would clean out all the versions and reinstall 1.9.1 - then when you install gems they will be placed correctly under 1.9.1

The inability to handle POST requests was made by others. There is
some hacks out there to get around it, but I don't like to resort to
them.

> going back to 1.8.7 is simply going backwards - 1.9.1 is the current "official" version (and offers lots of improvements) . I understand those who are already with 1.8.x not wanting to upgrade (ain't broke, don't fix) but if you're starting, you really should be in the 1.9.1 series (a few old gems might hiccup but can usually be quickly fixed)

As already mentioned there is hacks to get around this issue, so it is
hard to trust 1.9 when things like that are required. I do admit that
I am not a live on the edge of code type, I like the assurance that it
will work 100% :)

> >>>>>>> phusion-passen...@googlegroups.com<phusion-passenger%2Bunsubscr...
>
> read more »

[MilesTogoe]

On 12/10/2009 01:11 PM, chris wrote:
> Miles,
>
>
>> 1) with 1.9.1 gems are built in so you don't need "require 'rubygems' " but having it shouldn't give errors either
>>
> This only happened once I told passenger to use Ruby 1.8
>
>
>> 2) since you're getting gem errors odds are you might have messed up your gems switching between versions. Personally I would clean out all the versions and reinstall 1.9.1 - then when you install gems they will be placed correctly under 1.9.1
>>
> The inability to handle POST requests was made by others. There is
> some hacks out there to get around it, but I don't like to resort to
> them.
>
>
>> going back to 1.8.7 is simply going backwards - 1.9.1 is the current "official" version (and offers lots of improvements) . I understand those who are already with 1.8.x not wanting to upgrade (ain't broke, don't fix) but if you're starting, you really should be in the 1.9.1 series (a few old gems might hiccup but can usually be quickly fixed)
>>
> As already mentioned there is hacks to get around this issue, so it is
> hard to trust 1.9 when things like that are required. I do admit that
> I am not a live on the edge of code type, I like the assurance that it
> will work 100% :)
>

Huh ? In my experience this is totally wrong - we have no problem with
"Posts" - which sounds more like a web programming problem anyway than a
language problem. There seems to be this BS that 1.9.1 is on the "edge"
- the language core team says it's the official version, our experience
shows it works fine, Rails says it's 100% 1.9.1 compatible, Rack is
compatible, Passenger is compatible, Sinatra is compatible, ...... - so
let's stop this BS and move forward. If some older gems are not
compatible then they should get fixed thru submitted comments or
patches,etc.

Hey, you don't even know how the gems work and you're saying it's on the
edge or needs hacks.

btw Firefox 3.5 broke Firebug, Adblock, etc - this didn't stop people
from upgrading or say the new version was on the edge ... and the
plugins quickly got updated - that's the way software works.

>> read more �

>>
> --
>
> You received this message because you are subscribed to the Google Groups "Phusion Passenger Discussions" group.
> To post to this group, send email to phusion-...@googlegroups.com.

[chris]

Now breathe slowly Miles and think happy thoughts.

Using the latest version of ruby would be nice, but it WAS causing me
issues. Do I want to wait for a fix? Not really. Will I take another
stab at using Ruby 1.9? Yes I will.

> Hey, you don't even know how the gems work and you're saying it's on the edge or needs hacks.

You're right. So obviously I am not worthy of wasting anymore of your
precious time.

> >>>>>>>>> phusion_passenger/abstract_server.rb:352:in `main_loop'...
>
> read more »