I think I get this as well when I use puppetrun. Are you by change using passenger at all? -Jason On Apr 1, 2009, at 12:03 PM, chris wrote:
> > > Puppet's been super for our installation of ~800 hosts, but I'm trying > to figure out why puppetrun isn't working for our us. Nodes work fine > as clients, but when I try to use puppetrun, everything looks fine on > the client side: > > puppetd -d -v --no-daemonize gives: > ... > notice: Finished catalog run in 21.81 seconds > info: access[puppetrunner]: allowing serv3.local xxx.xxx.xxx.xxx > access > > and /var/log/messages: > Apr 1 14:56:10 host0101 puppetd[29243]: (access[puppetrunner]) > allowing serv3.local xxx.xxx.xxx.xxx access > > but the server side simply gives: > > [r...@serv3 httpd]# puppetrun --host host0101.local --debug > debug: Parsing /etc/puppet/puppet.conf > debug: Puppet::Network::Client::Runner: defining puppetrunner.run > Triggering host0101.local > debug: Calling puppetrunner.run > err: Could not call puppetrunner.run: #<RuntimeError: HTTP-Error: 500 > Internal Server Error > > Host host0101.local failed: HTTP-Error: 500 Internal Server Error > host0101.local finished with exit code 2 > Failed: host0101.local > > I'm not even sure where to start looking for what's causing this -- > any suggestions on how to get to the bottom of this? > > Many thanks, > Chris > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---