I'm getting the same error with a new custom fact in <module>/lib. The puppetmaster is running on Apache2 + Passenger (setup works fine in production with 0.24.8).
With Puppet 2.6.0 (Debian package) the file is created empty. With Puppet 2.6.0 + patch from Brice, I get a 'Could not set file on ensure: Error 500' on the client side and the apache logs on the server shows: [Wed Aug 04 23:01:46 2010] [error] [client 192.168.200.199] Premature end of script headers: vzbackup.rb [ pid=28420 file=ext/apache2/Hooks.cpp:735 time=2010-08-04 23:01:46.242 ]: The backend application (process 28465) 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 1268:Fixnum) (process 28465): from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/request_handler.rb:100:in `process_request' from /var/lib/gems/1.8/gems/rack-1.2.1/lib/rack/utils.rb:305:in `each' from /var/lib/gems/1.8/gems/rack-1.2.1/lib/rack/utils.rb:304:in `each' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/request_handler.rb:96:in `process_request' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_request_handler.rb:207:in `main_loop' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:120:in `run' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:65:in `spawn_application' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/utils.rb:252:in `safe_fork' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:58:in `spawn_application' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/rack/application_spawner.rb:41:in `spawn_application' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:150:in `spawn_application' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/spawn_manager.rb:278:in `handle_spawn_application' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in `__send__' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:352:in `main_loop' from /var/lib/gems/1.8/gems/passenger-2.2.15/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously' from /var/lib/gems/1.8/gems/passenger-2.2.15/bin/passenger-spawn-server:61 Same thing with 2.6.1rc1 from git unfortunately... Apart from this, the manifests are compiled and run fine, and the facts that already exist on the client are evaluated correctly. The server I use for testing is running Ubuntu 10.04, the client is 8.04. I've tried various combinations of Passenger (2.2.7, 2.2.11, 2.2.15) and Rack (1.1.0, 1.2.1), from gems and .deb, without success. Here is my current gems list on the server: 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.2.1) rails (2.3.8) rake (0.8.7) I'll take any suggestion! Thanks, Nico On 03/08/10 20:24, Richard Crowley wrote: >> Passenger is still the preferred way to scale a puppetmaster (until I >> progress on the JRuby front). > > I've had great success running Puppet 0.25.4, 0.25.5, and 2.6.0 under > Nginx and Unicorn. Alas, http://projects.puppetlabs.com/issues/4319 > is still in play. I use the highly suspect "give up and use wget" > workaround. Use either 2.6.1rc1 or my single-line patch linked to the bug report to get rid of the issue :) IMHO it's better than refactoring your manifests to wget stuff. -- Brice Figureau My Blog: http://www.masterzen.fr/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@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.
