Noticed I was running passenger 2.2.3 (which did work for 0.24) so I
upgraded to 2.2.5.
After restarting one of my 0.25 nodes started working, but the other
one still gets:
warning: peer certificate won't be verified in this SSL session
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:55:in
`deserialize': Error 403 on SERVER: Forbidden (Net::HTTPError)
from /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb:69:in `find'
In the master logs I get a strange error
Sep 8 16:20:52 s_lo...@sl01 puppetmasterd[3581]: Denying access:
Forbidden request: sl03.temp.local(192.168.1.110) access to
/certificate/ca [find] authenticated at line 0
Sep 8 16:20:52 s_lo...@sl01 puppetmasterd[3581]: Forbidden request:
sl03.temp.local(192.168.1.110) access to /certificate/ca [find]
authenticated at line 0
What's strange is that the DNS name it's quoting is not the DNS for that IP.
2009/9/8 Matt <mattmora...@gmail.com>:
> I'm currently upgrading our puppetmaster to 0.25, at first just using
> the standard webrick install to get the modules working.
> Both my new 0.25 clients and existing 0.24 clients had no problem connecting.
>
> I've now changed the puppetmaster over to run under passenger, my 0.24
> clients are still connecting, but my 0.25 clients are now getting:
>
> err: Could not retrieve catalog from remote server: Error 403 on
> SERVER: Forbidden
> warning: Not using cache on failed catalog
> err: Could not retrieve catalog; skipping run
>
> Do I need to clean all the ssl's of the 0.25 clients?
>
> 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
-~----------~----~----~----~------~----~------~--~---
