Did anyone find a resolution to this problem? I am getting the same thing with Solaris and have tried both 2.2.2 and 2.2.5 and get "Error 400 on SERVER: Bad Request" with both versions.
passenger-status seems to work properly: passenger-status ----------- General information ----------- max = 12 count = 0 active = 0 inactive = 0 Waiting on global queue: 0 On Oct 21, 1:31 am, Stephen Nelson-Smith <sanel...@gmail.com> wrote: > On Tue, Oct 20, 2009 at 9:36 PM, Matt <mattmora...@gmail.com> wrote: > > > I'd really bite the bullet Stephen and givepassenger2.2.2 a try. > > OK - triedpassenger2.2.2 - same behaviour. > > I'm going to blow everything away and start again from scratch and see > if I get the same results. > > S. > -- > Stephen Nelson-Smith > Technical Director > Atalanta Systems Ltdwww.atalanta-systems.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
