I'll give that a bash and see if it stops the kickstart clients getting a 500.
Thanks, Matt 2009/9/25 Ohad Levy <ohadl...@gmail.com>: > Hi Matt, > > Sicne foreman is a rails app, you dont need the config.ru (its only rack > applications which require it). > > if you have passenger enabled somehwere in you apache conf, all you need is > something like: > <VirtualHost *:80> > ServerName foreman.mydomain > DocumentRoot /var/rails/foreman/public/ > </VirtualHost> > > Cheers, > Ohad > On Fri, Sep 25, 2009 at 4:44 AM, Matt <mattmora...@gmail.com> wrote: >> >> Hi all, >> >> Anyone have an example on how they're running foreman under passenger. >> I've tried with the config.ru from >> foreman/vendor/rails/railties/dispatches/config.ru >> >> I can access the application fine, but when my clients try to receive >> the kickstart file they get a 500 error - >> 192.168.0.2 - - [24/Sep/2009:12:04:44 +0100] "GET >> /unattended/kickstart HTTP/1.0" 500 613 "-" "anaconda/11.1.2.168" >> >> The error in the foreman log is: >> >> [Thu Sep 24 12:04:38 2009] [notice] Apache/2.2.11 (Unix) DAV/2 >> Phusion_Passenger/2.2.2 configured -- resuming normal operations >> Error during failsafe response: closed stream >> [Thu Sep 24 12:04:46 2009] [error] [client 192.168.0.2] Premature end >> of script headers: kickstart >> [ pid=2736 file=ext/apache2/Hooks.cpp:553 time=2009-09-24 12:04:46.484 ]: >> Backend process 2748 did not return a valid HTTP response. It >> returned: [X-Powered-By] >> *** Exception NoMethodError in >> PhusionPassenger::Rack::ApplicationSpawner (undefined method `each' >> for nil:NilClass) (process 2748): >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/rack/request_handler.rb:85:in >> `process_request' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/abstract_request_handler.rb:203:in >> `main_loop' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/rack/application_spawner.rb:110:in >> `run' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/rack/application_spawner.rb:67:in >> `spawn_application' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/utils.rb:181:in >> `safe_fork' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/rack/application_spawner.rb:60:in >> `spawn_application' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/rack/application_spawner.rb:45:in >> `spawn_application' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/spawn_manager.rb:158:in >> `spawn_application' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/spawn_manager.rb:282:in >> `handle_spawn_application' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/abstract_server.rb:337:in >> `__send__' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/abstract_server.rb:337:in >> `main_loop' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/lib/phusion_passenger/abstract_server.rb:187:in >> `start_synchronously' >> from >> /usr/lib64/ruby/gems/1.8/gems/passenger-2.2.2/bin/passenger-spawn-server:61 >> [Thu Sep 24 12:05:23 2009] [notice] caught SIGTERM, shutting down >> >> If I go back to using web brick the clients grab the kickstart okay. >> >> Thanks, >> >> Matt >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
