Puppet

Hi chaps

Looking at the files in there I swear it’s server-side caching of client details! The dir doesn’t exist on the client, and on the server I see ./facts and ./node – the facts sent back to the PM broadly.

To be honest I was expecting the ./node dir to be the entire localconfig.yaml file but they are just the facts, m'lud.

<0> root@engpsr0170.etf.barcapetf.com (0 jobs)
 /var/lib/puppet/yaml
  # find
.
./node
./node/engpsr0171.etf.barcapetf.com.yaml
./node/engpsr0170.etf.barcapetf.com.yaml
./facts
./facts/engpsr0171.etf.barcapetf.com.yaml
./facts/engpsr0170.etf.barcapetf.com.yaml

Cheers, Derek

The directory named ‘yaml’ is the server yaml directory, not the client yaml directory (normally named ‘client_yaml’).

Can you provide a stack trace from the process that is failing because this directory doesn’t exist?

All appropriate yaml dirs get created fine for me…

Sorry, you’re right, must have gotten confused. On the client puppetd run:

info: Caching catalog for engpsr0170.etf.barcapetf.com
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/yaml.rb:36:in `mkdir'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/yaml.rb:36:in `save'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb:201:in `find'
/usr/lib/ruby/site_ruby/1.8/puppet/indirector.rb:51:in `find'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:94:in `retrieve_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:425:in `thinmark'
/usr/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/active_support/core_ext/benchmark.rb:10:in `realtime'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:424:in `thinmark'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:93:in `retrieve_catalog'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:132:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:130:in `with_client'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:51:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application/puppetd.rb:103:in `onetime'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
/usr/sbin/puppetd:159
err: Could not retrieve catalog from remote server: No such file or directory - /var/lib/puppet/client_yaml/catalog
err: Could not retrieve catalog; skipping run

So, we start off with $vardir=/var/lib/puppet This exists by way of either our build process, the puppet RPM or autocreation (or possibly all three).

Then I fire off puppetd as above. Judging from the stack trace, it tries to create /var/lib/puppet/client_yaml/catalog, and fails because /var/lib/puppet/client_yaml does not exist. A manual mkdir of /var/lib/puppet/client_yaml is sufficient to get puppetd up and running.

Best regards, Derek