Puppet users - Jan 2011 - Configuration not applied, Finished catalog run in 0.01 seconds

Hello,
I have installed puppet on the machine that is supposed to be the
puppet server.
Puppet is version 2.6.4
The puppet.conf file is the default created with puppet --genconfig >
puppet.conf

When launching puppetd on the client and after having signed the
certificate, I always get the same
info: Caching catalog for pc001
info: Applying configuration version ''1296044901''
notice: Finished catalog run in 0.01 seconds

it doesn''t matter what I change in my site on the server, the
configuration is never applied.


In debug mode:
debug: Failed to load library ''rubygems'' for feature
''rubygems''
debug: Failed to load library ''selinux'' for feature
''selinux''
debug: Failed to load library ''shadow'' for feature
''libshadow''
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderUser_role_add: file roledel does
not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting
false
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/
dscl does not exist
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature
microsoft_windows is missing
debug: Failed to load library ''ldap'' for feature
''ldap''
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/
puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/client_data]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/
puppet]
debug: /File[/etc/puppet/ssl/certs/pc001.pem]: Autorequiring File[/etc/
puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/
ssl]
debug: /File[/etc/puppet/ssl/private_keys/pc001.pem]: Autorequiring
File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/
puppet]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/
puppet/ssl/certs]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring File[/var/
lib/puppet]
debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/
ssl]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/
puppet/ssl]
debug: /File[/var/lib/puppet/state/classes.txt]: Autorequiring File[/
var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring File[/var/
lib/puppet/state]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/
ssl]
debug: /File[/etc/puppet/ssl/public_keys/pc001.pem]: Autorequiring
File[/etc/puppet/ssl/public_keys]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring File[/
var/lib/puppet/state]
debug: Finishing transaction 23930165622580
debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs/pc001.pem]: Autorequiring File[/etc/
puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/private_keys/pc001.pem]: Autorequiring
File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/
puppet]
debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/
puppet/ssl]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/
ssl]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/
ssl]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring File[/etc/
puppet/ssl]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/
puppet]
debug: /File[/etc/puppet/ssl/public_keys/pc001.pem]: Autorequiring
File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring File[/etc/
puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/
ssl]
debug: Finishing transaction 23930165887920
debug: Using cached certificate for ca
debug: Using cached certificate for pc001
debug: Finishing transaction 23930165452760
debug: Loaded state in 0.00 seconds
debug: Using cached certificate for ca
debug: Using cached certificate for pc001
debug: Using cached certificate_revocation_list for ca
debug: catalog supports formats: b64_zlib_yaml dot marshal pson raw
yaml; using pson
info: Caching catalog for pc001
debug: Creating default schedules
debug: Loaded state in 0.00 seconds
info: Applying configuration version ''1296044901''
debug: Finishing transaction 23930164414940
debug: Storing state
debug: Stored state in 0.00 seconds
notice: Finished catalog run in 0.02 seconds


Any ideas? I cannot understand why it doesn''t work.
Thanks for your help!
Adriana

-- 
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.

Hi Adriana,

Can you paste the output of:

puppetd --test --noop --evaltrace

and:

cat /var/lib/puppet/classes.txt

and your node definition for the host ''pc001''.

-Luke

On Jan 26, 1:19 pm, Adriana <adriana.tele...@gmail.com>
wrote:
> Hello,
> I have installed puppet on the machine that is supposed to be the
> puppet server.
> Puppet is version 2.6.4
> The puppet.conf file is the default created with puppet --genconfig >
> puppet.conf
...
> info: Applying configuration version ''1296044901''
> debug: Finishing transaction 23930164414940
> debug: Storing state
> debug: Stored state in 0.00 seconds
> notice: Finished catalog run in 0.02 seconds
>
> Any ideas? I cannot understand why it doesn''t work.
> Thanks for your help!
> Adriana
-- 
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 Wed, 26 Jan 2011 05:19:11 -0800 (PST)
Adriana Adriana wrote:
> Hello,
Hi,

[...]
> When launching puppetd on the client and after having signed the
> certificate, I always get the same
> info: Caching catalog for pc001
> info: Applying configuration version ''1296044901''
> notice: Finished catalog run in 0.01 seconds
> it doesn''t matter what I change in my site on the server, the
> configuration is never applied.
what is it supposed to do? could you please paste your site/node files?
is pc001 the real hostname? did you include it without domain?

**simple try will be adding a file in site.pp.

Cheers,
Arnau

-- 
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.

Hello,
here it is:

puppetd --server pc03 --test --noop --evaltrace
info: Caching catalog for aldaqpc001.cern.ch
info: Applying configuration version ''1296044901''
info: /Schedule[puppet]: Evaluated in 0.00 seconds
info: /Schedule[daily]: Evaluated in 0.00 seconds
info: /Schedule[monthly]: Evaluated in 0.00 seconds
info: /Schedule[never]: Evaluated in 0.00 seconds
info: /Schedule[weekly]: Evaluated in 0.00 seconds
info: /Schedule[hourly]: Evaluated in 0.00 seconds
info: /Filebucket[puppet]: Evaluated in 0.00 seconds
notice: Finished catalog run in 0.02 seconds


cat /var/lib/puppet/classes.txt
settings

For the node definition on the server I use
File:
# site.pp

import "nodes.pp"

File nodes.pp

import "classes/*.pp"

node "pc001" {

    include ldc
}
node "pc002" {

    include test
}
node "pc003" {

    include gdc
}

where ldc is a class.

Thanks for your help!
Cheers,
Adriana
On Jan 26, 2:24 pm, "luke.bigum" <luke.bi...@fasthosts.co.uk>
wrote:
> Hi Adriana,
>
> Can you paste the output of:
>
> puppetd --test --noop --evaltrace
>
> and:
>
> cat /var/lib/puppet/classes.txt
>
> and your node definition for the host ''pc001''.
>
> -Luke
>
> On Jan 26, 1:19 pm, Adriana <adriana.tele...@gmail.com> wrote:
>
> > Hello,
> > I have installed puppet on the machine that is supposed to be the
> > puppet server.
> > Puppet is version 2.6.4
> > The puppet.conf file is the default created with puppet --genconfig
>
> > puppet.conf
> ...
> > info: Applying configuration version ''1296044901''
> > debug: Finishing transaction 23930164414940
> > debug: Storing state
> > debug: Stored state in 0.00 seconds
> > notice: Finished catalog run in 0.02 seconds
>
> > Any ideas? I cannot understand why it doesn''t work.
> > Thanks for your help!
> > Adriana
-- 
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.

Even if I completely delete the manifests dir content, the result is
the same.
It looks like the client cannot download the configuration from the
server, but I don''t see any errors related to that.
Cheers,
Adriana

On Jan 26, 2:27 pm, Adriana <adriana.tele...@gmail.com>
wrote:
> Hello,
> here it is:
>
> puppetd --server pc03 --test --noop --evaltrace
> info: Caching catalog for aldaqpc001.cern.ch
> info: Applying configuration version ''1296044901''
> info: /Schedule[puppet]: Evaluated in 0.00 seconds
> info: /Schedule[daily]: Evaluated in 0.00 seconds
> info: /Schedule[monthly]: Evaluated in 0.00 seconds
> info: /Schedule[never]: Evaluated in 0.00 seconds
> info: /Schedule[weekly]: Evaluated in 0.00 seconds
> info: /Schedule[hourly]: Evaluated in 0.00 seconds
> info: /Filebucket[puppet]: Evaluated in 0.00 seconds
> notice: Finished catalog run in 0.02 seconds
>
> cat /var/lib/puppet/classes.txt
> settings
>
> For the node definition on the server I use
> File:
> # site.pp
>
> import "nodes.pp"
>
> File nodes.pp
>
> import "classes/*.pp"
>
> node "pc001" {
>
>     include ldc}
>
> node "pc002" {
>
>     include test}
>
> node "pc003" {
>
>     include gdc
>
> }
>
> where ldc is a class.
>
> Thanks for your help!
> Cheers,
> Adriana
> On Jan 26, 2:24 pm, "luke.bigum"
<luke.bi...@fasthosts.co.uk> wrote:
>
> > Hi Adriana,
>
> > Can you paste the output of:
>
> > puppetd --test --noop --evaltrace
>
> > and:
>
> > cat /var/lib/puppet/classes.txt
>
> > and your node definition for the host ''pc001''.
>
> > -Luke
>
> > On Jan 26, 1:19 pm, Adriana <adriana.tele...@gmail.com> wrote:
>
> > > Hello,
> > > I have installed puppet on the machine that is supposed to be the
> > > puppet server.
> > > Puppet is version 2.6.4
> > > The puppet.conf file is the default created with puppet
--genconfig >
> > > puppet.conf
> > ...
> > > info: Applying configuration version
''1296044901''
> > > debug: Finishing transaction 23930164414940
> > > debug: Storing state
> > > debug: Stored state in 0.00 seconds
> > > notice: Finished catalog run in 0.02 seconds
>
> > > Any ideas? I cannot understand why it doesn''t work.
> > > Thanks for your help!
> > > Adriana
-- 
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 01/26/2011 02:37 PM, Adriana wrote:
> Even if I completely delete the manifests dir content, the result is
> the same.
> It looks like the client cannot download the configuration from the
> server, but I don''t see any errors related to that.
> Cheers,
> Adriana
Weird, there should be an error about no fitting node definition found
or somesuch.

Can you make absolutely certain that you talk to the correct puppet
master (i.e., watch its logs)?
Also, you may want to run the puppet master in the foreground with debug
output as well.

HTH,
Felix

-- 
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.

It is very strange, the /var/log/messages on the server says:

pc03 puppet-master[32210]: Compiled catalog for pc001 in environment
production in 0.03 seconds
but then the rigth catalog is not downloaded.


On Jan 26, 2:42 pm, Felix Frank <felix.fr...@alumni.tu-berlin.de>
wrote:
> On 01/26/2011 02:37 PM, Adriana wrote:
>
> > Even if I completely delete the manifests dir content, the result is
> > the same.
> > It looks like the client cannot download the configuration from the
> > server, but I don''t see any errors related to that.
> > Cheers,
> > Adriana
>
> Weird, there should be an error about no fitting node definition found
> or somesuch.
>
> Can you make absolutely certain that you talk to the correct puppet
> master (i.e., watch its logs)?
> Also, you may want to run the puppet master in the foreground with debug
> output as well.
>
> HTH,
> Felix
-- 
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 01/26/2011 03:01 PM, Adriana wrote:
> It is very strange, the /var/log/messages on the server says:
> 
> pc03 puppet-master[32210]: Compiled catalog for pc001 in environment
> production in 0.03 seconds
> but then the rigth catalog is not downloaded.
> 
Oh, another guess: You''re using the wrong site.pp and it includes a
default node.
So there''s no error, and you get no resources/classes etc.

Find it. Run the puppetmaster with debug output if necessary.

Cheers,
Felix

-- 
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.

info: access[^/catalog/([^/]+)$]: allowing ''method'' find
info: access[^/catalog/([^/]+)$]: allowing * access
info: access[/certificate_revocation_list/ca]: allowing
''method'' find
info: access[/certificate_revocation_list/ca]: allowing * access
info: access[/report]: allowing ''method'' save
info: access[/report]: allowing * access
info: access[/file]: allowing * access
Running the server in foreground with the debug option gives me this
when the client runs puppet.

info: access[/certificate/ca]: adding authentication no
info: access[/certificate/ca]: allowing ''method'' find
info: access[/certificate/ca]: allowing * access
info: access[/certificate/]: adding authentication no
info: access[/certificate/]: allowing ''method'' find
info: access[/certificate/]: allowing * access
info: access[/certificate_request]: adding authentication no
info: access[/certificate_request]: allowing ''method'' find
info: access[/certificate_request]: allowing ''method'' save
info: access[/certificate_request]: allowing * access
info: access[/]: adding authentication any
info: Inserting default ''/status''(auth) acl because none where
found
in ''/etc/puppet/auth.conf''
info: Expiring the node cache of pc001
info: Not using expired node for pc001 from cache; expired at Wed Jan
26 15:27:43 +0100 2011
info: Caching node for pc001

So I guess it takes the configuration fro a catalog somewhere but I
don''t know how to disable it.
Do you know if it is possible to use the puppetmaster without
auth.conf?
Thanks.
Adriana
On Jan 26, 3:12 pm, Felix Frank <felix.fr...@alumni.tu-berlin.de>
wrote:
> On 01/26/2011 03:01 PM, Adriana wrote:
>
> > It is very strange, the /var/log/messages on the server says:
>
> > pc03 puppet-master[32210]: Compiled catalog for pc001 in environment
> > production in 0.03 seconds
> > but then the rigth catalog is not downloaded.
>
> Oh, another guess: You''re using the wrong site.pp and it includes
a
> default node.
> So there''s no error, and you get no resources/classes etc.
>
> Find it. Run the puppetmaster with debug output if necessary.
>
> Cheers,
> Felix
-- 
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.

> So I guess it takes the configuration fro a catalog somewhere but I
> don''t know how to disable it.
> Do you know if it is possible to use the puppetmaster without
> auth.conf?
That''s not a problem.

Hm, the puppet master debug output doesn''t tell you anything about the
manifest in use.
You may want to try
strace -f -e trace=file puppet master ... 2>&1 | grep site.pp to learn
what manifest it opens.

Big hammers, but what''re you going to do...? ;-)

Well, of course you *can* have another look in your puppet.conf before
that, and see what manifest that configures. But that''s so boring :)

Cheers,
Felix

-- 
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.

I am sorry but I don''t understand what you are suggesting me to do
with
 strace -f -e trace=file puppet master ... 2>&1 | grep site.pp
where do I have to look for site.pp?


On Jan 26, 3:41 pm, Felix Frank <felix.fr...@alumni.tu-berlin.de>
wrote:
> > So I guess it takes the configuration fro a catalog somewhere but I
> > don''t know how to disable it.
> > Do you know if it is possible to use the puppetmaster without
> > auth.conf?
>
> That''s not a problem.
>
> Hm, the puppet master debug output doesn''t tell you anything about
the
> manifest in use.
> You may want to try
> strace -f -e trace=file puppet master ... 2>&1 | grep site.pp to
learn
> what manifest it opens.
>
> Big hammers, but what''re you going to do...? ;-)
>
> Well, of course you *can* have another look in your puppet.conf before
> that, and see what manifest that configures. But that''s so boring
:)
>
> Cheers,
> Felix
-- 
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 01/26/2011 03:47 PM, Adriana wrote:
> I am sorry but I don''t understand what you are suggesting me to do
> with
>  strace -f -e trace=file puppet master ... 2>&1 | grep site.pp
> where do I have to look for site.pp?
"puppet master ..." is the invocation of the puppet master with your
usual arguments. site.pp should be in the output of grep.

-- 
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.

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.


On Jan 26, 3:49 pm, Felix Frank <felix.fr...@alumni.tu-berlin.de>
wrote:
> On 01/26/2011 03:47 PM, Adriana wrote:
>
> > I am sorry but I don''t understand what you are suggesting me
to do
> > with
> >  strace -f -e trace=file puppet master ... 2>&1 | grep site.pp
> > where do I have to look for site.pp?
>
> "puppet master ..." is the invocation of the puppet master with
your
> usual arguments. site.pp should be in the output of grep.
-- 
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 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 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.

£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 <felix.fr...@alumni.tu-berlin.de>
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 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.

The result is the same and no message "We''re going insane"
appears.
I am without hope...I don''t know..


On Jan 26, 4:38 pm, "luke.bigum" <luke.bi...@fasthosts.co.uk>
wrote:
> £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 <felix.fr...@alumni.tu-berlin.de>
> 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 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.

And the puppet.conf change? Nothing? Can you try put a typo in
puppet.conf (say, egwedgewdgswrhbrhbre) and then run your puppet
master daemon in the foreground verbosely and complain like this:

[root@puppet-ca ~]# puppetmasterd --no-daemonize --verbose
err: Could not parse /etc/puppet/puppet.conf: Could not match line
dgvdagvdagvdagvag at /etc/puppet/puppet.conf:dgvdagvdagvdagvag
notice: Starting Puppet master version 2.6.3
notice: Caught INT; calling stop

On Jan 26, 4:12 pm, Adriana <adriana.tele...@gmail.com>
wrote:
> The result is the same and no message "We''re going
insane" appears.
> I am without hope...I don''t know..
>
> On Jan 26, 4:38 pm, "luke.bigum"
<luke.bi...@fasthosts.co.uk> wrote:
>
> > £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
<felix.fr...@alumni.tu-berlin.de>
> > 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 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.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This is going out on a limb, but is your manifest file in UNIX format?

dos2unix <file>

And try again.

Puppet will skip files it doesn''t understand from what I remember
having
made this mistake a couple of times.

Trevor

On 01/26/2011 11:12 AM, Adriana wrote:
> The result is the same and no message "We''re going
insane" appears.
> I am without hope...I don''t know..
> 
> 
> On Jan 26, 4:38 pm, "luke.bigum"
<luke.bi...@fasthosts.co.uk> wrote:
>> Ł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 <felix.fr...@alumni.tu-berlin.de>
>> 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
> 
- -- 
Trevor Vaughan
 Vice President, Onyx Point, Inc.
 email: tvaughan@onyxpoint.com
 phone: 410-541-ONYX (6699)
 pgp: 0x6C701E94

- -- This account not approved for unencrypted sensitive information --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEbBAEBAgAGBQJNQF4RAAoJECNCGV1OLcypNvQH+MuzaFqRVZ7wEUdZ4eXVDXB1
7PgNeU3Th2F7XzXqfPWmWJPGNpbaIXCSYFU79+11dCaw09EO+s3se9LfzQdp1avg
k8XYt+6CF5mljfqorc1kjTgIVGp4izm74oG6bHRL8EpjB/qu9+dDSkSApOBxHUCY
nG4I2ndHpOnajniu3eanINHrb3f8xXEVx+3uLd1tBh7dlHTr7FeqYxGQghdK7dvK
PRNfuzeBO0LdTFhMO9qyfmJkTFMcBqkgoYZXQICZ7aRtn7esNzPP9CVBoYRCQbcB
ChFR8yXkp0tfINct+Rzxyeeyc8w6DV48Y4AbRW83o0s9KXCCYlFZh/8NJN6Obg==U+We
-----END PGP SIGNATURE-----

-- 
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 Wed, Jan 26, 2011 at 05:27:56AM -0800, Adriana wrote:
> Hello,
> here it is:
> 
> puppetd --server pc03 --test --noop --evaltrace
> info: Caching catalog for aldaqpc001.cern.ch
So your puppet master is pc03 and you puppet client is
aldaqpc001.cern.ch. Is this correct?
> For the node definition on the server I use
> File:
> # site.pp
> 
> import "nodes.pp"
> 
> File nodes.pp
> 
> import "classes/*.pp"
> 
> node "pc001" {
> 
>     include ldc
> }
> node "pc002" {
> 
>     include test
> }
> node "pc003" {
> 
>     include gdc
> }
> 
> where ldc is a class.
1) you dont have a nodedefintion for aldaqpc001 or
aldaqpc001.cern.ch so none of you nodedefinition are applied.

2) just to be sure here: There is actual content like a
fileresource or anything in the class ldc right? Because If there is no
file/mount/cron/whatever resource definition in your class you wont see
anything.

3) If you use puppet --genconfig and redirect right to puppet.conf make
sure you dont have a »genconfig = true« line in it. Also make sure you
havent created /etc/puppet.conf but /etc/puppet/puppet.conf

-Stefan

On Wed, Jan 26, 2011 at 09:46, Trevor Vaughan <tvaughan@onyxpoint.com>
wrote:

G''day Trevor.
> This is going out on a limb, but is your manifest file in UNIX format?
> dos2unix <file>
> And try again.
>
> Puppet will skip files it doesn''t understand from what I remember
having
> made this mistake a couple of times.
Seriously?  Interesting problem; was it sufficient to have a perfectly
valid manifest that was in DOS (CR-LF) format for it to be skipped?
Did you hit it with ''puppet apply'', or just the full
master/agent
setup?

I would love to create a bug for this, because "silently" is a bad
thing: we should either work, or complain about not working, not just
silently ignore anything.

Regards,
     Daniel
-- 
⎋ Puppet Labs Developer – http://puppetlabs.com
✉ Daniel Pittman <daniel@puppetlabs.com>
✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775
♲ Made with 100 percent post-consumer electrons

-- 
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 Wed, 26 Jan 2011, Daniel Pittman wrote:
> I would love to create a bug for this, because "silently" is a
bad
> thing: we should either work, or complain about not working, not just
> silently ignore anything.
See issue #4690 and issue #3514.

--apb (Alan Barrett)

-- 
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.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Daniel,

Just for completeness, I saw it using a server/client setup and it was
one of those cases with something trying too hard to be correct which
resulted in the new files just being ignored.

They could be read, so it wasn''t a permissions error and the bugs that
Alan posted seem to be pretty much spot on.

I''ve been testing with 2.6 but until a few more bugs are fixed, I
can''t
push forward with any sort of serious upgrade. I know they''re on the
radar, so we''ll get there and hopefully many of these issues will
vanish.

Thanks,

Trevor

On 01/26/2011 02:21 PM, Daniel Pittman wrote:
> On Wed, Jan 26, 2011 at 09:46, Trevor Vaughan
<tvaughan@onyxpoint.com> wrote:
> 
> G''day Trevor.
> 
>> This is going out on a limb, but is your manifest file in UNIX format?
>> dos2unix <file>
>> And try again.
>>
>> Puppet will skip files it doesn''t understand from what I
remember having
>> made this mistake a couple of times.
> 
> Seriously?  Interesting problem; was it sufficient to have a perfectly
> valid manifest that was in DOS (CR-LF) format for it to be skipped?
> Did you hit it with ''puppet apply'', or just the full
master/agent
> setup?
> 
> I would love to create a bug for this, because "silently" is a
bad
> thing: we should either work, or complain about not working, not just
> silently ignore anything.
> 
> Regards,
>      Daniel
- -- 
Trevor Vaughan
 Vice President, Onyx Point, Inc.
 email: tvaughan@onyxpoint.com
 phone: 410-541-ONYX (6699)
 pgp: 0x6C701E94

- -- This account not approved for unencrypted sensitive information --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJNQPKmAAoJECNCGV1OLcyps+wH/0fzjFkCrhewWqctMtxJ2FBM
M7ZyfC4DjivFUp6CDhQ51RNuPgjTQVSbncCiIGxAOf/bBFtYN9GefuTZNtgdIysb
cbVGzS4SvBicd1lzXHOQDE6HPGnypKqyqB//CYQWWajMCq6AMGMhJdusMZFPSlgL
/jxg/Pxla5v3zj1j7il3THMAgn37m7ivZNqTSLf5PK2G0vaYAt232uIY1Fh/g/Ro
x6I7evDe1C+qHuQv/U07tXsIw6pQS4u2Ajs+8m5DpskNPH+rm0yLDWTDwYpP044I
NYzjlRwZCrP1izCxYG1vlUtlirFJZmRvardl2+1TrfSLi3FeBvqoS+0WCe7qIyQ=BleC
-----END PGP SIGNATURE-----

-- 
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.

Thanks for that.  Pointers are just as good as details. :)
     Daniel

On Wed, Jan 26, 2011 at 20:20, Trevor Vaughan <tvaughan@onyxpoint.com>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Daniel,
>
> Just for completeness, I saw it using a server/client setup and it was
> one of those cases with something trying too hard to be correct which
> resulted in the new files just being ignored.
>
> They could be read, so it wasn''t a permissions error and the bugs
that
> Alan posted seem to be pretty much spot on.
>
> I''ve been testing with 2.6 but until a few more bugs are fixed, I
can''t
> push forward with any sort of serious upgrade. I know they''re on
the
> radar, so we''ll get there and hopefully many of these issues will
vanish.
>
> Thanks,
>
> Trevor
>
> On 01/26/2011 02:21 PM, Daniel Pittman wrote:
>> On Wed, Jan 26, 2011 at 09:46, Trevor Vaughan
<tvaughan@onyxpoint.com> wrote:
>>
>> G''day Trevor.
>>
>>> This is going out on a limb, but is your manifest file in UNIX
format?
>>> dos2unix <file>
>>> And try again.
>>>
>>> Puppet will skip files it doesn''t understand from what I
remember having
>>> made this mistake a couple of times.
>>
>> Seriously?  Interesting problem; was it sufficient to have a perfectly
>> valid manifest that was in DOS (CR-LF) format for it to be skipped?
>> Did you hit it with ''puppet apply'', or just the full
master/agent
>> setup?
>>
>> I would love to create a bug for this, because "silently" is
a bad
>> thing: we should either work, or complain about not working, not just
>> silently ignore anything.
>>
>> Regards,
>>      Daniel
>
> - --
> Trevor Vaughan
>  Vice President, Onyx Point, Inc.
>  email: tvaughan@onyxpoint.com
>  phone: 410-541-ONYX (6699)
>  pgp: 0x6C701E94
>
> - -- This account not approved for unencrypted sensitive information --
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
>
> iQEcBAEBAgAGBQJNQPKmAAoJECNCGV1OLcyps+wH/0fzjFkCrhewWqctMtxJ2FBM
> M7ZyfC4DjivFUp6CDhQ51RNuPgjTQVSbncCiIGxAOf/bBFtYN9GefuTZNtgdIysb
> cbVGzS4SvBicd1lzXHOQDE6HPGnypKqyqB//CYQWWajMCq6AMGMhJdusMZFPSlgL
> /jxg/Pxla5v3zj1j7il3THMAgn37m7ivZNqTSLf5PK2G0vaYAt232uIY1Fh/g/Ro
> x6I7evDe1C+qHuQv/U07tXsIw6pQS4u2Ajs+8m5DpskNPH+rm0yLDWTDwYpP044I
> NYzjlRwZCrP1izCxYG1vlUtlirFJZmRvardl2+1TrfSLi3FeBvqoS+0WCe7qIyQ> =BleC
> -----END PGP SIGNATURE-----
>


-- 
⎋ Puppet Labs Developer – http://puppetlabs.com
✉ Daniel Pittman <daniel@puppetlabs.com>
✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775
♲ Made with 100 percent post-consumer electrons

-- 
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.

Hello,
I finally found the problem, there were two reasons:
- in the client there was the file /etc/puppet.conf, removing it made
the client dowloading the right configuraition
- after I was installing the complete manifests site and classes
through an rpm which copied all the files to the new puppet server,
after that nothing was working anymore. The reason was that the rpm
was setting the permission to 644 and instead it should have been 755,
at least for the directories manifests, files and classes.
Now it works!
Thanks a lot for your help!
Adriana

On Jan 27, 5:50 am, Daniel Pittman <dan...@puppetlabs.com>
wrote:
> Thanks for that.  Pointers are just as good as details. :)
>      Daniel
>
>
>
> On Wed, Jan 26, 2011 at 20:20, Trevor Vaughan
<tvaug...@onyxpoint.com> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
>
> > Hi Daniel,
>
> > Just for completeness, I saw it using a server/client setup and it was
> > one of those cases with something trying too hard to be correct which
> > resulted in the new files just being ignored.
>
> > They could be read, so it wasn''t a permissions error and the
bugs that
> > Alan posted seem to be pretty much spot on.
>
> > I''ve been testing with 2.6 but until a few more bugs are
fixed, I can''t
> > push forward with any sort of serious upgrade. I know they''re
on the
> > radar, so we''ll get there and hopefully many of these issues
will vanish.
>
> > Thanks,
>
> > Trevor
>
> > On 01/26/2011 02:21 PM, Daniel Pittman wrote:
> >> On Wed, Jan 26, 2011 at 09:46, Trevor Vaughan
<tvaug...@onyxpoint.com> wrote:
>
> >> G''day Trevor.
>
> >>> This is going out on a limb, but is your manifest file in UNIX
format?
> >>> dos2unix <file>
> >>> And try again.
>
> >>> Puppet will skip files it doesn''t understand from
what I remember having
> >>> made this mistake a couple of times.
>
> >> Seriously?  Interesting problem; was it sufficient to have a
perfectly
> >> valid manifest that was in DOS (CR-LF) format for it to be
skipped?
> >> Did you hit it with ''puppet apply'', or just the
full master/agent
> >> setup?
>
> >> I would love to create a bug for this, because
"silently" is a bad
> >> thing: we should either work, or complain about not working, not
just
> >> silently ignore anything.
>
> >> Regards,
> >>      Daniel
>
> > - --
> > Trevor Vaughan
> >  Vice President, Onyx Point, Inc.
> >  email: tvaug...@onyxpoint.com
> >  phone: 410-541-ONYX (6699)
> >  pgp: 0x6C701E94
>
> > - -- This account not approved for unencrypted sensitive information
--
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.11 (GNU/Linux)
>
> > iQEcBAEBAgAGBQJNQPKmAAoJECNCGV1OLcyps+wH/0fzjFkCrhewWqctMtxJ2FBM
> > M7ZyfC4DjivFUp6CDhQ51RNuPgjTQVSbncCiIGxAOf/bBFtYN9GefuTZNtgdIysb
> > cbVGzS4SvBicd1lzXHOQDE6HPGnypKqyqB//CYQWWajMCq6AMGMhJdusMZFPSlgL
> > /jxg/Pxla5v3zj1j7il3THMAgn37m7ivZNqTSLf5PK2G0vaYAt232uIY1Fh/g/Ro
> > x6I7evDe1C+qHuQv/U07tXsIw6pQS4u2Ajs+8m5DpskNPH+rm0yLDWTDwYpP044I
> > NYzjlRwZCrP1izCxYG1vlUtlirFJZmRvardl2+1TrfSLi3FeBvqoS+0WCe7qIyQ>
> =BleC
> > -----END PGP SIGNATURE-----
>
> --
> ⎋ Puppet Labs Developer –http://puppetlabs.com
> ✉ Daniel Pittman <dan...@puppetlabs.com>
> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775
> ♲ Made with 100 percent post-consumer electrons
-- 
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.