I think that I''m running into the warning on external node support here but after a recent upgrade for my puppetmaster I get: puppetmasterd[19397]: Could not find aa0-006-4.foo.com with names aa0-006-4.foo.com, aa0-006-4 I''ve not changed puppetd.conf which contains: ldapnodes = true ldapserver = my.ldap.foo.com ldapbase = ou=hosts,dc=foo,dc=com I''ve not explicitly set external_nodes (so it stays false). What else needs to be done? Cheers, Ryan
On 6/20/07 10:52 AM, "Ryan Dooley" <rd@powerset.com> wrote:> I think that I''m running into the warning on external node support here but > after a recent upgrade for my puppetmaster I get: > > puppetmasterd[19397]: Could not find aa0-006-4.foo.com with names > aa0-006-4.foo.com, aa0-006-4 > > I''ve not changed puppetd.conf which contains: > > ldapnodes = true > ldapserver = my.ldap.foo.com > ldapbase = ou=hosts,dc=foo,dc=com > > I''ve not explicitly set external_nodes (so it stays false). > > What else needs to be done?I should probably also mention that I only updated the puppetmaster and not the clients. Do the clients need to go hand in hand with the master? Cheers, Ryan
On Jun 20, 2007, at 12:52 PM, Ryan Dooley wrote:> I think that I''m running into the warning on external node support > here but > after a recent upgrade for my puppetmaster I get: > > puppetmasterd[19397]: Could not find aa0-006-4.foo.com with names > aa0-006-4.foo.com, aa0-006-4 > > I''ve not changed puppetd.conf which contains: > > ldapnodes = true > ldapserver = my.ldap.foo.com > ldapbase = ou=hosts,dc=foo,dc=com > > I''ve not explicitly set external_nodes (so it stays false). > > What else needs to be done?Puppetd.conf? I hope you at least mean puppetmasterd.conf, or preferably puppet.conf (note the lack of a ''d''). And no, you don''t need to update your clients. -- While one person hesitates because he feels inferior, the other is busy making mistakes and becoming superior. -- Henry C. Link --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
> Puppetd.conf? I hope you at least mean puppetmasterd.conf, or > preferably puppet.conf (note the lack of a ''d'').Yes but since puppet uses one configuration file now... :-)> And no, you don''t need to update your clients.That''s what I thought. Cheers, Ryan
On 6/20/07 12:52 PM, "Ryan Dooley" <rd@powerset.com> wrote:> >> Puppetd.conf? I hope you at least mean puppetmasterd.conf, or >> preferably puppet.conf (note the lack of a ''d''). > > Yes but since puppet uses one configuration file now... :-)Okay... Strange indeed (either that or I''m losing my sight). I had setup symlinks for puppet.conf to puppetd.conf and puppetmasterd.conf. As soon as I removed the links and just left puppet.conf in place, puppetmasterd lit up and the errors disappeared. Cheers, Ryan
On Jun 20, 2007, at 3:00 PM, Ryan Dooley wrote:> > Okay... Strange indeed (either that or I''m losing my sight). I had > setup > symlinks for puppet.conf to puppetd.conf and puppetmasterd.conf. > As soon as > I removed the links and just left puppet.conf in place, > puppetmasterd lit up > and the errors disappeared.If the old configuration files exist, Puppet will use those in preference (and throw a warning). The parsing process for the old files is different from the new files, so that could be why you got such different behaviour. -- An ounce of action is worth a ton of theory. --Friedrich Engels --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com