In the catalog, /Settings[*] is what?

[nicholas]

I left my new puppetmasterd running last night.
came in with a stack trace below.

A number of questions:

1. Where did /Settings come from?

2. Is there a way to dump the contents of the catalog to understand?

3. I want to change the perms for all that stuff

4. puppetd is not running on this host, does puppetmasterd act like a
puppetd?


notice: Compiled catalog for inst01.corp.631h.metaweb.com in 0.20
seconds
notice: Reparsing /etc/puppet/puppet.conf
warning: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/
log/puppet]/owner: Cannot manage ownership unless running as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[main]/File[/var/
lib/puppet/ssl]/owner: Cannot manage ownership unless running as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[metrics]/File[/
var/lib/puppet/rrd]/owner: Cannot manage ownership unless running as
root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/
puppet/ssl/ca]/owner: Cannot manage ownership unless running as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/
puppet/ssl/ca/serial]/owner: Cannot manage ownership unless running as
root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/
puppet/ssl/ca/inventory.txt]/owner: Cannot manage ownership unless
running as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/
puppet/ssl/ca/ca_crl.pem]/owner: Cannot manage ownership unless
running as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/
puppet/ssl/ca/requests]/owner: Cannot manage ownership unless running
as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/
puppet/ssl/ca/signed]/owner: Cannot manage ownership unless running as
root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/
puppet/ssl/ca/private]/owner: Cannot manage ownership unless running
as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/
puppet/ssl/ca/private/ca.pass]/owner: Cannot manage ownership unless
running as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/
puppet/ssl/ca/ca_crt.pem]/owner: Cannot manage ownership unless
running as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/
puppet/ssl/ca/ca_pub.pem]/owner: Cannot manage ownership unless
running as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[ca]/File[/var/lib/
puppet/ssl/ca/ca_key.pem]/owner: Cannot manage ownership unless
running as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[puppetmasterd]/
File[/var/lib/puppet/bucket]/owner: Cannot manage ownership unless
running as root
warning: /Settings[/etc/puppet/puppet.conf]/Settings[puppetmasterd]/
File[/var/log/puppet/masterhttp.log]/owner: Cannot manage ownership
unless running as root
err: /Settings[/etc/puppet/puppet.conf]/Settings[puppetmasterd]/File[/
etc/puppet/manifests]/ensure: change from absent to directory failed:
Could not set directory on ensure: Permission denied - /etc/puppet/
manifests
warning: /Settings[/etc/puppet/puppet.conf]/Settings[puppetmasterd]/
File[/var/lib/puppet/yaml]/owner: Cannot manage ownership unless
running as root
/usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:748:in `use': Got
1 failure(s) while initializing: change from absent to directory
failed: Could not set directory on ensure: Permission denied - /etc/
puppet/manifests (RuntimeError)
from /usr/lib/ruby/site_ruby/1.8/puppet/node/catalog.rb:136:in
`apply'
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:744:in `use'
from /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:724:in `use'
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:531:in
`reuse'
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:529:in
`each'
from /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:529:in
`reuse'
from /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
... 12 levels...
from /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event-
loop.rb:116:in `iterate'
from /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event-
loop.rb:107:in `run'
from /usr/lib/ruby/site_ruby/1.8/puppet.rb:320:in `start'
from /usr/sbin/puppetmasterd:285
[ro...@inst01.corp.631h puppet]# puppetmasterd --no-daemon --verbose

[Peter Meier]

Hi

> A number of questions:
>
> 1. Where did /Settings come from?

how did you start your puppetmasterd, as which user?

> 2. Is there a way to dump the contents of the catalog to understand?

this is not part of the catalog, puppetmasterd tries to create an
environment itself like it should be.

> 3. I want to change the perms for all that stuff

if you run it as root it should do it, there have been a little bug in
past which still shows that however that should be fixed in 0.24.8 or at
least in the upcoming version.

> 4. puppetd is not running on this host, does puppetmasterd act like a
> puppetd?

nope, it just tries to create/manage the environment like it should be
to run fine. but look for the bug mentioned above.

cheers pete

[nicholas]

Puppetmasterd runs as root, though I suppose I could start it as
puppet

The main thing I am trying to do here is not have the CA directory,
and all its files owned by root
I want all the CA stuff to continue to be owned by the puppet user.

I guess what I mean is that I want to be able to specify the perms for
the files in the /Settings "catalog".
I am guessing that it is all hard coded more or less.

n