Thanks for the reply Keith. I will definitively have to dig into the
auth.conf, but the auth.conf I am using is the one created when I run
./puppet-enterprise-installer as per the PE 2.7 quickstart guide. Is there
a way to let puppetlabs know that there is a problem during the evaluation
period?
You could try adding:
On 25 March 2013 16:50, Red Cricket red.cricket.b...@gmail.com wrote:
Thanks for the reply Keith. I will definitively have to dig into the
auth.conf, but the auth.conf I am using is the one created when I run
./puppet-enterprise-installer as per the PE 2.7 quickstart
You could try adding:
path /facts
auth any
method find, search
allow *
before the deny entry at the end of the file and restarting your Puppet
master.
Or look for a similar entry and see if the allow line contains a specific
hostname or IP that doesn't match what you expect.
I don't know about
Thanks again for your help Keith, but I am still having the same issue ...
I changed the auth.conf from this ...
$ cat /etc/puppetlabs/puppet/auth.conf_save
path ~ ^/catalog/([^/]+)$
method find
auth yes
allow $1
path ~ ^/node/([^/]+)$
method find
auth yes
allow $1
path
Puppet runs fine on RHEL 6.2. It looks like your auth.conf is missing some
entries. Do you perhaps have an auth.conf.rpmnew you need to move into
place?
- Keith
Hi All,
I am trying to follow the documentation at this link:
http://docs.puppetlabs.com/pe/latest/quick_start.html
When I get to
