Puppet users - Jan 2013 - Configuration is not applied notice: Finished catalog run in 0.01 seconds

Hi guys,

I am fairly new to puppet and I am having a problem with one of the 
clients. I recently installed a new server that should get config from 
puppet master. All similar servers I recently installed didn''t have any
problem. I installed puppet agent on the server and sent a sign request. 
SSL cert is signed but when I run puppetd manually I get the following:

info: Retrieving plugin
info: Caching catalog for client4
info: Applying configuration version ''1357214285''
notice: Finished catalog run in 0.01 seconds

Even though it says catalog run finish nothing is applied. The strange 
thing is that I recently installed the same OS on the same machine and 
didn''t get any problem. I tried various debug options but searching the
output didn''t help.  

debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl 
does not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not 
exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Failed to load library ''rubygems'' for feature
''rubygems''
debug: Failed to load library ''selinux'' for feature
''selinux''
debug: Puppet::Type::File::ProviderMicrosoft_windows: feature 
microsoft_windows is missing
debug: Failed to load library ''ldap'' for feature
''ldap''
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring 
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys/client4.pem]: Autorequiring 
File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/crl.pem]: 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/clientbucket]: Autorequiring 
File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs/client4.pem]: Autorequiring 
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/client_data]: Autorequiring 
File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring 
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys/client4.pem]: Autorequiring 
File[/etc/puppet/ssl/private_keys]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring 
File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring 
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring 
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring 
File[/var/lib/puppet/state]
debug: Finishing transaction 70254557004780
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
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/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring 
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring 
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys/client4.pem]: Autorequiring 
File[/etc/puppet/ssl/private_keys]
debug: /File[/etc/puppet/ssl/public_keys/client4.pem]: Autorequiring 
File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/certs/client4.pem]: Autorequiring 
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: Finishing transaction 70254556183860
debug: Using cached certificate for ca
debug: Using cached certificate for client4
debug: Finishing transaction 70254557715260
debug: Loaded state in 0.00 seconds
info: Retrieving plugin
debug: Loaded state in 0.00 seconds
debug: Using cached certificate for ca
debug: Using cached certificate for client4
debug: Using cached certificate_revocation_list for ca
debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using 
pson
debug: /File[/var/lib/puppet/lib]: Storing newly-audited value  for content
debug: Finishing transaction 70254557493280
debug: Storing state
debug: Stored state in 0.00 seconds
debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson
info: Caching catalog for client4
debug: Creating default schedules
debug: Loaded state in 0.00 seconds
info: Applying configuration version ''1357160285''
debug: Finishing transaction 70254556072440
debug: Storing state
debug: Stored state in 0.00 seconds
notice: Finished catalog run in 0.01 seconds

I assume it is not configuration on the puppet master side as this should 
be applied to default nodes (and it works on any other machine). Sorry for 
pretty general input but can you please advise in which direction I should 
go in order to fix it?

Cheers,

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/du4HcEyqAYsJ.
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,

First thing I would is check where I think this node is declared and stick a
notify there to spit out a message on the run.

node nodename {
  notify {"some message and maybe a $var or $::fact
 }

Then use that same kind of message to trace through your code and find out the
path your node travels.

That should get you further along.

Den

On 04/01/2013, at 2:08, Aleksandar Nikolic <aleksnikolic@gmail.com> wrote:
> Hi guys,
> 
> I am fairly new to puppet and I am having a problem with one of the
clients. I recently installed a new server that should get config from puppet
master. All similar servers I recently installed didn''t have any
problem. I installed puppet agent on the server and sent a sign request. SSL
cert is signed but when I run puppetd manually I get the following:
> 
> info: Retrieving plugin
> info: Caching catalog for client4
> info: Applying configuration version ''1357214285''
> notice: Finished catalog run in 0.01 seconds
> 
> Even though it says catalog run finish nothing is applied. The strange
thing is that I recently installed the same OS on the same machine and
didn''t get any problem. I tried various debug options but searching the
output didn''t help.
> 
> debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl
does not exist
> debug: Puppet::Type::User::ProviderLdap: true value when expecting false
> debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
exist
> debug: Puppet::Type::User::ProviderPw: file pw does not exist
> debug: Failed to load library ''rubygems'' for feature
''rubygems''
> debug: Failed to load library ''selinux'' for feature
''selinux''
> debug: Puppet::Type::File::ProviderMicrosoft_windows: feature
microsoft_windows is missing
> debug: Failed to load library ''ldap'' for feature
''ldap''
> debug: /File[/var/lib/puppet/client_yaml]: Autorequiring
File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/public_keys/client4.pem]: Autorequiring
File[/etc/puppet/ssl/public_keys]
> debug: /File[/etc/puppet/ssl/crl.pem]: 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/clientbucket]: Autorequiring
File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/certs/client4.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
> debug: /File[/var/lib/puppet/client_data]: Autorequiring
File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/private_keys/client4.pem]: Autorequiring
File[/etc/puppet/ssl/private_keys]
> debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
File[/var/lib/puppet/state]
> debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
> debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
> debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
> debug: Finishing transaction 70254557004780
> debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
> 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/crl.pem]: Autorequiring File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
> debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
> debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
> debug: /File[/var/lib/puppet/run]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/private_keys/client4.pem]: Autorequiring
File[/etc/puppet/ssl/private_keys]
> debug: /File[/etc/puppet/ssl/public_keys/client4.pem]: Autorequiring
File[/etc/puppet/ssl/public_keys]
> debug: /File[/etc/puppet/ssl/certs/client4.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
> debug: /File[/var/lib/puppet/log]: Autorequiring File[/var/lib/puppet]
> debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
> debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
> debug: Finishing transaction 70254556183860
> debug: Using cached certificate for ca
> debug: Using cached certificate for client4
> debug: Finishing transaction 70254557715260
> debug: Loaded state in 0.00 seconds
> info: Retrieving plugin
> debug: Loaded state in 0.00 seconds
> debug: Using cached certificate for ca
> debug: Using cached certificate for client4
> debug: Using cached certificate_revocation_list for ca
> debug: file_metadata supports formats: b64_zlib_yaml pson raw yaml; using
pson
> debug: /File[/var/lib/puppet/lib]: Storing newly-audited value  for content
> debug: Finishing transaction 70254557493280
> debug: Storing state
> debug: Stored state in 0.00 seconds
> debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using
pson
> info: Caching catalog for client4
> debug: Creating default schedules
> debug: Loaded state in 0.00 seconds
> info: Applying configuration version ''1357160285''
> debug: Finishing transaction 70254556072440
> debug: Storing state
> debug: Stored state in 0.00 seconds
> notice: Finished catalog run in 0.01 seconds
> 
> I assume it is not configuration on the puppet master side as this should
be applied to default nodes (and it works on any other machine). Sorry for
pretty general input but can you please advise in which direction I should go in
order to fix it?
> 
> Cheers,
> -- 
> You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
> To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/du4HcEyqAYsJ.
> 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.
-- 
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 Thursday, January 3, 2013 9:08:48 AM UTC-6, Aleksandar Nikolic
wrote:
>
> Hi guys,
>
> I am fairly new to puppet and I am having a problem with one of the 
> clients. I recently installed a new server that should get config from 
> puppet master. All similar servers I recently installed didn''t
have any
> problem. I installed puppet agent on the server and sent a sign request. 
> SSL cert is signed but when I run puppetd manually I get the following:
>
> info: Retrieving plugin
> info: Caching catalog for client4
> info: Applying configuration version ''1357214285''
> notice: Finished catalog run in 0.01 seconds
>
> Even though it says catalog run finish nothing is applied. The strange 
> thing is that I recently installed the same OS on the same machine and 
> didn''t get any problem. I tried various debug options but
searching the
> output didn''t help.  
>
>
As Denmat implied, this looks like a problem at your master.  It recognizes 
the client, but serves up an empty catalog.  That probably means that the 
node block you think will match the client does not in fact match it, but 
there are other possibilities.


John

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/6sWqd96pz8UJ.
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.