> [Thu Jul 29 18:03:00 2010] [error] [client 136.168.1.4] Premature end of script headers: preamble
> [ pid=28460 file=ext/apache2/Hooks.cpp:735 time=2010-07-29 18:03:00.77 ]:
> The backend application (process 30417) didn't send a valid HTTP response. It might have crashed during the middle of sending an HTTP response, so please check whether there are crashing problems in your application. This is the data that it sent: [Content-Type]
> *** Exception NoMethodError in PhusionPassenger::Rack::ApplicationSpawner (undefined method `each' for 3238:Fixnum) (process 30417):
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/request_handler.rb:100:in `process_request'
> from /usr/local/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/utils.rb:278:in `each'
> from /usr/local/lib/ruby/gems/1.8/gems/rack-1.1.0/lib/rack/utils.rb:277:in `each'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/request_handler.rb:96:in `process_request'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_request_handler.rb:207:in `main_loop'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:120:in `run'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:65:in `spawn_application'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/utils.rb:252:in `safe_fork'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:58:in `spawn_application'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:41:in `spawn_application'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:150:in `spawn_application'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:278:in `handle_spawn_application'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in `__send__'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in `main_loop'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously'
> from /usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15/bin/passenger-spawn-server:61
--
Russell A Jackson <r...@csub.edu>
Network Analyst
California State University, Bakersfield
--
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.
# gem list
*** LOCAL GEMS ***
actionmailer (2.3.8)
actionpack (2.3.8)
activerecord (2.3.8)
activeresource (2.3.8)
activesupport (2.3.8)
fastthread (1.0.7)
passenger (2.2.15)
rack (1.1.0)
rails (2.3.8)
rake (0.8.7)
ruby-augeas (0.3.0)
sources (0.0.2)
>
> On Mon, Aug 2, 2010 at 1:17 PM, Russell Jackson <r...@csub.edu> wrote:
>
>> I'm having a hell of a time with mod_passenger. Where would I even begin
>> to investigate where this exception is coming from? My configuration
>> works fine with the 2.6.0 webrick server.
>>
Yep. Got the modified one for the puppetmaster -> server class rename.
Can I take this to mean that you have a working passenger installation
of 2.6.0? Knowing that it can work would at least narrow it down to a
local installation issue rather than a bug in puppet.
Same here. Worked in 0.25.5. Stopped working 2.6.0.
--
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.
On 08/02/2010 10:35 AM, Christopher Johnston wrote:Can I take this to mean that you have a working passenger installation
of 2.6.0? Knowing that it can work would at least narrow it down to a
local installation issue rather than a bug in puppet.
I have a working 2.6.0 passenger config albeit with passenger .11 not
.15 - Jeff McCune I believe tested Puppet with the latest Passenger and
discovered it did not work.
Regards
James
--
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571
Confirmed.
It just happens that the node I was using to test against had a such a
manifest. Tested against a node that didn't, and I didn't get the error.
--
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.
Can anyone experiencing the same issue try the following patch:
http://github.com/masterzen/puppet/commit/4d48437d0102d46cedd865973b97db49bcc862d2
and let us know if that solves or not the issue?
--
Brice Figureau
My Blog: http://www.masterzen.fr/