I ran the command puppet agent --configprint confdir on both the master and
the agetn and got the below for both. On the puppet master that is where
the puppet.conf file is in /etc/puppet directory.
[root@ct-eng-pup puppet]# puppet agent --configprint confdir
/etc/puppet
[root@ct-eng-pup
Ok so Puppet is reading /etc/puppet/puppet.conf. The timestamp on this file
shows is hasn't been changed for a few days though.
Is the output of:
# puppet agent --configprint moduledir
# puppet agent --configprint manifestdir
on the master what you expect?
Perhaps you have a permissions /
I ran the commands and I see that puppt is still pointing to /etc/puppet
not /etc/puppet2 for both modules and manifests, see below.
[root@ct-eng-pup etc]# puppet agent --configprint manifestdir
/etc/puppet/manifests
[root@ct-eng-pup etc]# puppet agent --configprint modulepath
What section of /etc/puppet/puppet.conf is your moduledir etc set in? This
should be in [main] or [master] - see the 'Config Blocks' section in the
docs.
Alternatively perhaps the master has not actually been restarted somehow
and is still using the old config.
- Keith
On 4 Mar 2013 21:54,
The paths below are in the main part of the puppet.conf file and I just
restart the puppet master process again and still nothing. I am thinking of
creating a production directory in /etc/puppet like so /etc/puppet/prod and
makeing the change in /etc/puppet/puppet.conf file to see if that
Moved the modules and manifests into /etc/puppet/prod and changed
/etc/puppet/puppet.conf. Then I restart the puppet master but does not work.
The entries in /etc/puppet/puppet.conf looks like this now.
# Where puppet master looks for its manifests.
# The default value is
