Passenger barfs.

157 views
Skip to first unread message

Douglas Garstang

unread,
Jun 24, 2010, 7:50:03 PM6/24/10
to Puppet Users
I have a freshly installed and updated CentOS 5.4 system running
puppet 0.25.5. I followed the passenger docs here:

http://projects.puppetlabs.com/projects/puppet/wiki/Using_Passenger

Upon starting the client, the following appears in the apache error log.

[Thu Jun 24 10:48:40 2010] [error] [client 10.10.4.45] Premature end
of script headers: production
[ pid=6785 file=ext/apache2/Hooks.cpp:706 time=2010-06-24 10:48:40.476 ]:
The backend application (process 7077) did not send a valid HTTP
response; instead, it sent nothing at all. It is possible that it has
crashed; please check whether there are crashing bugs in this
application.
*** Exception TypeError in PhusionPassenger::Rack::ApplicationSpawner
(can't convert Array into String) (process 7077):
from /usr/lib/ruby/gems/1.8/gems/rack-1.2.1/lib/rack/utils.rb:138:in
`union'
from /usr/lib/ruby/gems/1.8/gems/rack-1.2.1/lib/rack/utils.rb:138
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
from /usr/lib/ruby/gems/1.8/gems/rack-1.2.1/lib/rack/request.rb:1
from /usr/lib/ruby/site_ruby/1.8/puppet/network/http/rack.rb:35:in
`call'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/request_handler.rb:92:in
`process_request'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_request_handler.rb:207:in
`main_loop'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:120:in
`run'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:65:in
`spawn_application'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/utils.rb:252:in
`safe_fork'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:58:in
`spawn_application'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:41:in
`spawn_application'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:150:in
`spawn_application'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:278:in
`handle_spawn_application'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in
`__send__'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in
`main_loop'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:196:in
`start_synchronously'
from /usr/lib/ruby/gems/1.8/gems/passenger-2.2.15/bin/passenger-spawn-server:61

Anyone got any ideas?

Doug.

Gary Larizza

unread,
Jun 24, 2010, 8:12:56 PM6/24/10
to puppet...@googlegroups.com
Check Passenger version. Had this problem, rolled back to 2.2.9
(IIRC), removed the most recent Gem (2.2.11, I think), and all was
well.

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To post to this group, send email to puppet...@googlegroups.com.
> To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>
>

--
Gary Larizza

Director of Technology
Huron City Schools
http://www.huronhs.com


Silviu Paragina

unread,
Jun 24, 2010, 8:57:19 PM6/24/10
to puppet...@googlegroups.com
Also check the rack version, and the requirements for your version of
passenger. It smells like an incompatibility between the passenger
version and the rack version.
Aka what Gary said should be perfectly valid.


Silviu

Gary Larizza

unread,
Jun 24, 2010, 9:20:36 PM6/24/10
to puppet...@googlegroups.com
Yep - I narrowed it down to Rack and Passenger, but haven't tested for
exactly which one was the problem since I fixed it. I should have
probably submitted a bug. We were using OS X 10.6.4 Server, BTW.

Douglas Garstang

unread,
Jun 25, 2010, 1:48:55 AM6/25/10
to puppet...@googlegroups.com
On Thu, Jun 24, 2010 at 6:20 PM, Gary Larizza <ccs...@gmail.com> wrote:
> Yep - I narrowed it down to Rack and Passenger, but haven't tested for
> exactly which one was the problem since I fixed it.  I should have
> probably submitted a bug. We were using OS X 10.6.4 Server, BTW.
>
> On Thursday, June 24, 2010, Silviu Paragina <sil...@paragina.ro> wrote:
>> Also check the rack version, and the requirements for your version of passenger. It smells like an incompatibility between the passenger version and the rack version.
>> Aka what Gary said should be perfectly valid.

Ugh. Thanks. When I installed passenger, I got 2.1.15. I'm not a gem
user... don't use them. The web site
(http://blog.phusion.nl/2010/01/08/phusion-passenger-2-2-9-released/)
says to get 2.2.9 just do a 'gem install passenger' .... which is how
I got 2.2.15 installed.

Doug.

Douglas Garstang

unread,
Jun 25, 2010, 2:06:16 AM6/25/10
to puppet...@googlegroups.com

So, went to passenger 2.2.9. Still not working. Same error.


[root@inst01 httpd]# gem list

*** LOCAL GEMS ***

fastthread (1.0.7)
passenger (2.2.9)
rack (1.2.1)
rake (0.8.7)

[root@inst01 httpd]# ruby -v
ruby 1.8.5 (2006-08-25) [x86_64-linux]

[root@inst01 httpd]# rpm -qa | grep puppet
puppet-0.25.5-1.el5
puppet-server-0.25.5-1.el5

So... I don't have a clue...

Doug.

Gary Larizza

unread,
Jun 25, 2010, 7:14:25 AM6/25/10
to puppet...@googlegroups.com
Remove rack 1.2.1 first and then install rack 1.1.0.  It seems that rack 1.1.0 and passenger 2.2.9 have been the magic combination (at least for me).

-Gary


Doug.

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

alaric

unread,
Jul 15, 2010, 3:38:43 PM7/15/10
to Puppet Users
Hi Gary,

I just wanted to thank you for the post, I was running into this
exact same issue and rolling back to rack 1.1.0 worked for me. This
was really frustrating! I'm on RHEL5 using EPEL and Gems, so I felt
like I was being as vanilla as you could get!

Thanks again!


-a

On Jun 25, 7:14 am, Gary Larizza <ccsh...@gmail.com> wrote:
> Remove rack 1.2.1 first and then install rack 1.1.0.  It seems that rack
> 1.1.0 and passenger 2.2.9 have been the magic combination (at least for me).
>
> -Gary
>
> On Fri, Jun 25, 2010 at 2:06 AM, Douglas Garstang
> <doug.garst...@gmail.com>wrote:
>
>
>
> > On Thu, Jun 24, 2010 at 10:48 PM, Douglas Garstang
> > <doug.garst...@gmail.com> wrote:
> > puppet-users...@googlegroups.com<puppet-users%2Bunsu...@googlegroups.com>
> > .

Gary Larizza

unread,
Jul 15, 2010, 5:21:22 PM7/15/10
to puppet...@googlegroups.com
Glad I could help!

Last I heard, Jeff McCune was doing some tests with Passenger to figure out the best combination of Passenger/Rack.  He filed a bug (http://projects.puppetlabs.com/issues/4218), so be sure to Watch/Vote for it if you'd like to see it addressed.  

-Gary

To unsubscribe from this group, send email to puppet-users...@googlegroups.com.

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

Reply all
Reply to author
Forward
0 new messages