Hi James,
I think I've done it correctly.
Installed facter is 1.5.1 from lenny (package revision 0.1).
After one has installed the nis utils, we can set the domainname to a
domain to something thats not even remotely like your real domain (but
does exist in the global DNS).
Running "facter fqdn
Hmm. Any nisdomain with a dot does the trick to fool facter it seems.
# domainname uncle.wrinkle.puppy.reductivelabs
# facter fqdn
buildbox2.uncle.wrinkle.puppy.reductivelabs
# hostname --fqdn
buildbox2.domain.net
My point is, a nis domain doesn't need to be part of a hosts fqdn.
On Aug 7, 10:0
Right™.
The new facter from git does work correctly. I'll just upgrade.
Sorry for the noise.
On Aug 7, 10:18 am, Kai wrote:
> Hmm. Any nisdomain with a dot does the trick to fool facter it seems.
>
> # domainname uncle.wrinkle.puppy.reductivelabs
> # facter fqdn
> buildbox2.uncle.wrinkle.puppy
James Turnbull writes:
> This is the rc1 release of Puppet 0.25.0.
>
> It is available at:
>
> http://reductivelabs.com/downloads/puppet/puppet-0.25.0rc1.tar.gz
>
> This is not production ready code (almost though!) - it is a release
> candidate for testing.
There are now packages of puppet 0.25
On Aug 6, 9:03 pm, Steve Wray 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...
On Aug 6, 9:46 pm, Len Rugen wrote:
> OH! I'm pretty new at this and I think I know the answer :-)
>
> I don't think puppetd reads /etc/sysconfig/puppet (speaking redhat), I think
> the /etc/init.d/puppet script is what really reads the confiig file.
That's correct for the RedHat family of dis
> Prompted by this email, I went and created
> /var/lib/puppet/lib/puppet/type/iptables.rb on my puppetmaster. Doing
> so, causes things to work. Removing it leaves them working, at least
> till I restart puppetmaster, then it fails until I manually populate
> that. I'm not sure what how this shoul
I'd like to extend our Puppet installation to support split production
and development environments. We're using Subversion to manage Puppet
configurations and already have the recommended /etc/puppet layout to
handle a separate development branch.
What I'd like to do is have a centralized sourc
On Aug 7, 12:50 am, David Schmitt wrote:
> cnjohnson wrote:
> > I am running puppet-0.24.8 with passenger-2.2.2, apache-2.2.3 on RHEL
> > 5.2. I have two nodes, one x86_64 and one ppc64, that have the client
> > running and they are checking in regularly as expected. I have a
> > minimal site.pp
> Umm, I'm seeing this in my clients logs from puppetd, but only
> intermittently. Any any idea what it might mean?
puppet version, facter version, can you reproduce it and could you then
run it with --debug --trace ?
and what is the exact error, can you paste it?
cheers pete
--~--~-
On Sat, Aug 8, 2009 at 3:20 AM, Steven VanDevender wrote:
>
> However, what I'd really prefer to do is use the external node
> classifier only to supply the setting of the Puppet "environment"
> variable, and leave all of the class membership details in our existing
> nodes.pp (included from site.
I've tried to change logging to warn, it ended up breaking the puppetmaster
not being able to sign new certificates.
I know the setup in 0.25 is different, so it might work there.
Ohad
On Sat, Aug 8, 2009 at 3:30 AM, cnjohnson wrote:
>
> On Aug 7, 12:50 am, David Schmitt wrote:
> > cnjohnson
12 matches
Mail list logo