We use passenger and puppet 0.25.5 too. Since I've never figured out the right contents for namespaceauth.conf on the puppetmaster to avoid these 500 errors when performing puppetruns, we perform the following steps:
1. delete the namespaceauth.conf file on the puppetmaster 2. ensure that the the [puppetrunner] section in namespaceauth.conf on the client nodes contains the FQDN of the puppetmaster and not the puppet.our.domain CNAME. (I appreciate that this may well be due to the names we used for the puppet certs etc) With this setup, puppetd works on every node except the puppetmaster - not ideal, but not disastrous either - but we can successfully trigger puppetruns for any (other) node from the puppetmaster. On 12 February 2011 06:48, CraftyTech <hmmed...@gmail.com> wrote: > BTW: I'm using puppet 0.25.5 > > -- > 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. > -- 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.
