£10 says we're all missing something really obvious and we'll kick
ourselves afterwards ;)
Adriana, just confirm that in your puppet master's puppet.conf that
you generated with "puppetd --genconfig":
manifest = /etc/puppet/manifests/site.pp
That's what comes up for my version of Puppet (2.6.3). Can you replace
everything in that site.pp with this and only this:
node default {
notify { "woof": message => "We're going insane." }
}
And run your client again. And just as an aside can you do this:
grep -P -v '(#|^$)' /etc/puppet/puppet.conf
... Hmm, that's highlighted something... there's no [master] section.
I don't know if this is a problem or not, but if the above site.pp
doesn't shed any light, can you please put in this ultra simple
puppet.conf and try again:
[main]
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
factpath = $vardir/lib/facter
[agent]
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
[master]
manifest = /etc/puppet/manifests/site.pp
See how you go.
-Luke
On Jan 26, 3:07 pm, Felix Frank <[email protected]>
wrote:
> On 01/26/2011 04:03 PM, Adriana wrote:
>
> > The trace of the puppetmaster grepped with site gives me the right
> > site.
> > I cannot understand what happens.
> > It really looks like the client doesn't take the configuration at all.
>
> I'm stumped then. My last advice is to look hard and find out if there's
> a default node (or any node, such as "pc*") defined *anywhere* that may
> be clouding your attempts.
>
> Regards,
> Felix
--
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.
