On Sep 29, 4:44 pm, "Dave Nash" <[EMAIL PROTECTED]> wrote: > "puppetd --server=YOUR PUPPET MASTER" should get you rolling. I believe by > default puppet looks for a server named puppet in the DNS search path.
Okay, that solved the problem of not finding the server. Thanks! But didn't get me much further; I'm still not getting configuration data to the client. [EMAIL PROTECTED] ~]$ sudo puppetd --verbose --server=prcapp00 warning: peer certificate won't be verified in this SSL session notice: Did not receive certificate [ In between here I used puppetca on the server to sign the certificate ] notice: Got signed certificate notice: Starting Puppet client version 0.22.4 err: Could not retrieve configuration: Certificates were not trusted: hostname not match with the server certificate err: Could not run Puppet::Network::Client::Master: Cannot connect to server and there is no cached configuration I can't even tell for sure from this message which end had a problem with certificates, and I don't know what hostname it tried to check against which certificate. Reverse DNS on the client IP does get back the client name. Is puppet heavily intertwined with DNS? Like most people in commercial environments, I don't really have control over what DNS is doing with the names. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
