Thanks all for your input, the problem is solved. The environments worked
but I was testing with a file in a module that was not (yet) used. Sorry
for wasting your time.
On Thursday, December 19, 2013 2:21:48 PM UTC+1, Chantal Rosmuller wrote:
>
> Thank you Jeff,
>
> I changed $confdir to /etc/
Thank you Jeff,
I changed $confdir to /etc/puppet/ but it did not fix the issue.
On Tuesday, December 17, 2013 10:49:24 PM UTC+1, Jeff Bachtel wrote:
>
> There is a problem with variable hooks in puppet.conf that is fixed in
> the latest 3.4 release candidates (or so sayeth the bugreps).
>
> C
There is a problem with variable hooks in puppet.conf that is fixed in
the latest 3.4 release candidates (or so sayeth the bugreps).
Can you try explicitly specifying your directories instead of using
$confdir in that puppet.conf, at least to test?
Jeff
On 12/17/2013 09:18 AM, Chantal Rosmul
Thnaks, i tried but it didn't work. We do not start puppetmaster as a
standalone service so I stopped and started apache. (can that have anything
to do with the problem ?)
On Tuesday, December 17, 2013 3:08:41 PM UTC+1, John Pyeatt wrote:
>
> Not certain if this is the issue or not, but there se
Not certain if this is the issue or not, but there seems to be a bug in the
master regarding when the configuration file is read to override the
default settings. Try doing this:
1) start up your puppet master
2) after it is up and running try running this from the command line *touch
/etc/puppet
Hi,
On our puppet server the puppet environments do not seem to work. This is
our puppet.conf:
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
confdir=/etc/puppet
templatedir=$confdir/templates
modulepath=$confdi
I have a surprising problem with environments not working, i'm using rhel
6.3 with puppet-3.2.3-1.el6.noarch and here is the puppet.conf on the
master:
[main]
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
server = puppet.local
reports = store, http