Puppet is kicking my ass. Maybe I''m having a stupid day. Anyway -- currently working through the "Simplest Puppet Install Recipe" at <http://reductivelabs.com/trac/puppet/wiki/SimplestPuppetInstallRecipe>. Both client and server systems are Centos. Puppet[master] installed from RPMs, client has puppet-0.22.4-1.el5.rf (on Centos 5.2), server has puppet-server-0.22.4-1.el4.rf (on Centos 4.6). Putting in the simple sudo.pp class, and the site.pp as given, and starting the server (via the Redhat init script) went fine. Now, I start puppetd --verbose on the client. I''m supposed to see a message about not receiving a certificate. I don''t get one; I get: err: Could not find server puppet: getaddrinfo: Name or service not known err: Could not request certificate: Certificate retrieval failed: Could not find server puppet And I notice at this point that I wasn''t directed to configure the server name (or IP) anywhere. So I look at puppetd --help, and look at the online docs, and can''t find any hint about how you configure where the server is. So what''s up with that? It''s probably relevant to mention that the client is behind NAT on a private LAN (it''s part of a cluster behind LVS in NAT mode). The client system can connect out to other services on the same host as the puppet server, but if it''s depending on picking up server broadcasts or anything, that''s not going to fly. -- David Dyer-Bennet, dd-b@dd-b.net; http://dd-b.net/ Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/ Photos: http://dd-b.net/photography/gallery/ Dragaera: http://dragaera.info --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
David, David Dyer-Bennet wrote:> Puppet is kicking my ass. Maybe I''m having a stupid day. >Don''t worry it kicks my ass everyday, but I am training, and one day I''ll take it down I swear.> Anyway -- currently working through the "Simplest Puppet Install Recipe" > at > <http://reductivelabs.com/trac/puppet/wiki/SimplestPuppetInstallRecipe>. > Both client and server systems are Centos. Puppet[master] installed from > RPMs, client has puppet-0.22.4-1.el5.rf (on Centos 5.2), server has > puppet-server-0.22.4-1.el4.rf (on Centos 4.6). > > Putting in the simple sudo.pp class, and the site.pp as given, and > starting the server (via the Redhat init script) went fine. > > Now, I start puppetd --verbose on the client. I''m supposed to see a > message about not receiving a certificate. I don''t get one; I get: > > err: Could not find server puppet: getaddrinfo: Name or service not known > err: Could not request certificate: Certificate retrieval failed: Could not > find server puppet >As you can see, puppetd can''t resolve the ip address of your puppet server. Configure DNS or /etc/hosts on the client so that puppet.yourdomain.org can be resolved.> And I notice at this point that I wasn''t directed to configure the server > name (or IP) anywhere. So I look at puppetd --help, and look at the > online docs, and can''t find any hint about how you configure where the > server is. > > So what''s up with that? >Hmmm, that ain''t right. Will fix that in at least the wiki.> It''s probably relevant to mention that the client is behind NAT on a > private LAN (it''s part of a cluster behind LVS in NAT mode). The client > system can connect out to other services on the same host as the puppet > server, but if it''s depending on picking up server broadcasts or anything, > that''s not going to fly. > >No worries here puppetd is by default pull only. Just needs to be able to contact puppetmasterd and pull down its catalog. Hasta, teyo -- --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
On Sep 29, 11:26 pm, Teyo Tyree <t...@reductivelabs.com> wrote:> David Dyer-Bennet wrote: > > Puppet is kicking my ass. Maybe I''m having a stupid day. > > Don''t worry it kicks my ass everyday, but I am training, and one day > I''ll take it down I swear.I''m having hopes; but more for the long run than anything immediate :-).> > It''s probably relevant to mention that the client is behind NAT on a > > private LAN (it''s part of a cluster behind LVS in NAT mode). The client > > system can connect out to other services on the same host as the puppet > > server, but if it''s depending on picking up server broadcasts or anything, > > that''s not going to fly. > > No worries here puppetd is by default pull only. Just needs to be able > to contact puppetmasterd and pull down its catalog.Good. Thanks for confirming it! --~--~---------~--~----~------------~-------~--~----~ 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---