On Aug 6, 9:03 pm, Steve Wray <[email protected]> wrote:
> Steve Wray wrote:
[...]
> > something seems wrong...
>
> > This is all running under Debian Lenny.
>
> > r...@tec-lb1:/etc# puppetd --version
> > dnsdomainname: Unknown host
> > 0.24.5
>
> I just got the lenny-backport package.
>
> Same problem:
>
> r...@tec-lb1:/etc/apt# puppetd --version
> dnsdomainname: Unknown host
> 0.24.8
>
>
>
> > So.. from the 'dnsdomainname' ref there, it would seem to my untrained eye
> > that despite my best efforts in nsswitch.conf and host.conf, puppet is
> > trying DNS anyway...?
Try running the dnsdomainname program (or hostname --fqdn) from a
shell. I'd bet dollars to donuts that it gives you the same message.
If it does, then this is not a Puppet issue: it means that the system
resolver cannot resolve the system's own host name. I get similar
behavior with my puppet clients that acquire their hostname and IP
address via DHCP.
The diagnostic message is issued by facter (which you can test by
running facter directly from a shell prompt), and it is non-fatal, at
least for me. The effect on Puppet is simply that the 'dnsdomainname'
fact will not be available for the node.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
