So Chuck, it looks like you are set up to use what's called directory
environments. And I think your site.pp is not in the right place for that
setup.
This is in your master config:
environmentpath = $confdir/environments
And your agent is using the default environment, production.
So your site.pp should be located at:
$confdir/environments/production/manifests/site.pp
You can see what the value of $confdir is on your master by running:
sudo puppet config print confdir
This issue actually matches up perfectly with the behavior you're seeing.
The agent is running fine but there's just nothing for it to do because the
code you're testing is not in the site.pp that the master is actually
looking at. So when it compiles the catalog it's not including that
resource you're trying to test with.
If you add your code to the site.pp in that location I have a feeling it
will work.
This stuff around environments is honestly confusing at first. It was set
up so people can run their Puppet master against code in different Git
branches.
Rich
On Sat, Aug 29, 2015 at 12:24 PM Chuck Amadi <amadi.ch...@gmail.com> wrote:
> Hi Christopher and all,
>
> Utilised your crib troubleshooting checks and found out the following on
> the Master. Currently looking at working out these debug messages such as,
> *"Debug:
> Did not match path"*, but can you confirm if this is a possible reason
> for my nodes not pulling the manifests from the master ?
>
> "puppet master --debug --no-daemonize --color=false 2>&1 | tee
> /var/tmp/logm1" Procedure.
>
> # cat /var/tmp/logm1
>
> Debug: Evaluating match for Route /^\/v2\.0/
> Debug: Did not match path ("/production/catalog/chat.client.com")
>
> Debug: Evaluating match for Route /^\/v2\.0/
> Debug: Did not match path ("/production/reports/chat.client.com")
>
> Debug: Evaluating match for Route /^\/v2\.0/
> Debug: Did not match path ("/production/node/chat.client.com")
>
> Debug: Evaluating match for Route /^\/v2\.0/
> Debug: Did not match path ("/production/file_metadatas/pluginfacts")
>
> Data from chat.client.com logsc file.
>
> Debug: Loading external facts from /var/lib/puppet/facts.d
> Info: Loading facts
> Debug: Loading facts from /var/lib/puppet/lib/facter/puppet_vardir.rb
> Debug: Loading facts from /var/lib/puppet/lib/facter/root_home.rb
> Debug: Loading facts from /var/lib/puppet/lib/facter/concat_basedir.rb
> Debug: Loading facts from /var/lib/puppet/lib/facter/pe_version.rb
> Debug: Loading facts from /var/lib/puppet/lib/facter/facter_dot_d.rb
> Info: Loading facts
> Debug: Failed to load library 'msgpack' for feature 'msgpack'
>
> Debug: Puppet::Network::Format[msgpack]: feature msgpack is missing
> Debug: catalog supports formats: pson b64_zlib_yaml yaml dot raw
> Debug: Using cached connection for https://puppet.chat.client.com:8140
> Debug: Caching connection for https://puppet.chat.client.com:8140
> Info: Caching catalog for chat.client.com
>
> Debug: Creating default schedules
> Debug: Loaded state in 0.00 seconds
> Info: Applying configuration version '1440873225'
> Debug: Finishing transaction 70311483905180
> Debug: Storing state
> Debug: Stored state in 0.02 seconds
> Notice: Finished catalog run in 0.11 seconds
> Debug: Using cached connection for https://puppet.chat.client.com:8140
> Debug: Caching connection for https://puppet.chat.client.com:8140
> Debug: Closing connection for https://puppet.chat.client.com:8140
>
> I have checked the json and it appears that I have not pulled no .pp files
> from the master.
>
> # cat chat.client.json
>
>
> {"metadata":{"api_version":1},"document_type":"Catalog","data":{"resources":[{"title":"main","tags":["main","stage"],"type":"Stage","exported":false},{"title":"Settings","tags":["settings","class"],"type":"Class","exported":false},{"title":"Main","tags":["main","class"],"type":"Class","parameters":{"name":"main"},"exported":false}],"tags":["settings"],"environment":"production","version":1440873225,"classes":["settings"],"edges":[{"target":"Class[Settings]","source":"Stage[main]"},{"target":"Class[Main]","source":"Stage[main]"}],"name":"chat.client.json"}}
>
> Master puppet.conf file:
>
> [main]
> # The Puppet log directory.
> # The default value is '$vardir/log'.
> logdir = /var/log/puppet
>
> # Where Puppet PID files are kept.
> # The default value is '$vardir/run'.
> rundir = /var/run/puppet
>
> # Where SSL certificates are kept.
> # The default value is '$confdir/ssl'.
> ssldir = $vardir/ssl
> always_cache_features=true
> # Looking at using hiera key/value lookup to to config data for the
> future.
> hiera_config = $confdir/hiera.yaml
>
> server = puppet.master.com
> dns_alt_names = puppet, puppet.master.com, chat.client.com
> always_cache_features = true
> environment_timeout = unlimited
> environmentpath = $confdir/environments
> certname = puppet.master.com
> user = puppet
> group = puppet
> archive_files = true
> archive_file_server = puppet.master.com
>
> [master]
> environmentpath = $confdir/environments
> basemodulepath = $confdir/modules
>
> # This section is used by the Puppet agent application.
> [agent]
> # The file in which puppetd stores a list of the classes
> # associated with the retrieved configuratiion. Can be loaded in
> # the separate ``puppet`` executable using the ``--loadclasses``
> # option.
> # The default value is '$confdir/classes.txt'.
> report = true
> classfile = $vardir/classes.txt
>
> # Where puppetd caches the local configuration. An
> # extension indicating the cache format is added automatically.
> # The default value is '$confdir/localconfig'.
> localconfig = $vardir/localconfig
> graph = true
> pluginsync = true
> #pluginsync = false
> #environment = production
>
> chat.client.com puppet.conf file.
>
> [main]
> # The Puppet log directory.
> # The default value is '$vardir/log'.
> logdir = /var/log/puppet
> vardir=/var/lib/puppet
> # Where Puppet PID files are kept.
> # The default value is '$vardir/run'.
> rundir = /var/run/puppet
> #factpath=$vardir/lib/facter
> # Where SSL certificates are kept.
> # The default value is '$confdir/ssl'.
> ssldir = $vardir/ssl
> server = puppet.chat.client.com
> ordering = manifest
> certificate_revocation = false
>
> # This section is used by the Puppet agent application.
> [agent]
> # The file in which puppetd stores a list of the classes
> # associated with the retrieved configuratiion. Can be loaded in
> # the separate ``puppet`` executable using the ``--loadclasses``
> # option.
> # The default value is '$confdir/classes.txt'.
> #report = true
> classfile = $vardir/classes.txt
>
> server=puppet.chat.client.com
>
> # Where puppetd caches the local configuration. An
> # extension indicating the cache format is added automatically.
> # The default value is '$confdir/localconfig'.
> localconfig = $vardir/localconfig
> #graph = true
> #pluginsync = true
> #pluginsync = false
> # Have tried commenting this out, but nothing happened so kept the
> commented it for now.
> #environment = production
>
> Thanks for your help and advise.
>
>
>
> On Thursday, 27 August 2015 03:22:05 UTC+1, Chuck Amadi wrote:
>
>> Hi I Setup a Open Source Puppet Master and a Puppet Agent client on Linux
>> CentOS release 6.6, Puppet 3.8.1 on two separate servers.
>>
>> Have successfully setup communications between both servers (cert
>> list/sign/fingerprint etc etc and telnet 8140, disabled SELinux and added
>> iptables 8140 rule) and I have created and run "puppet apply site.pp"
>> node.pp and a init.pp/class no errors.
>>
>> Thus run "puppet master --verbose --no-daemonize" on the PM and "puppet
>> agent -t --debug" on the client and I do not receive any errors when I run
>> # puppet apply site.pp or node.pp etc or see any issues when I run tail on
>> the masterhttp.log file.
>>
>> Test files specified in site.pp and node.pp are created on the Puppet
>> Master but do not replicate to the Node ?
>>
>> Puppet node does not pick any changes from master's catalogs when I
>> forcibly restart puppet client or run puppet agent instead of waiting 30
>> mins, even though the "Info: Applying configuration version '1440626773'"
>> number changes accordingly. Further information below:
>>
>> # puppet master --verbose --no-daemonize
>>
>> Info: access[/file_metadata]: adding authentication any
>> Info: Inserting default '/status' (auth true) ACL
>> Info: Caching node for chat.client.com
>> Info: Caching node for chat.client.com
>> Notice: Compiled catalog for chat.client.com in environment production
>> in 0.04 seconds
>>
>> # puppet agent -t --debug
>>
>> Debug: Creating default schedules
>> Debug: Loaded state in 0.00 seconds
>> Info: Applying configuration version '1440626773' < changes >
>> Debug: Finishing transaction 69904202860300
>> Debug: Storing state
>> Debug: Stored state in 0.03 seconds
>> Notice: Finished catalog run in 0.13 seconds
>> Debug: Using cached connection for https://puppet.master.com:8140
>> Debug: Caching connection for https://puppet.master.com:8140
>> Debug: Closing connection for https://puppet.master.com:8140
>>
>> Any help or advice to troubleshoot on why Puppet node does not pull any
>> changes from master's site.pp and node.pp manifest. I'm ignoring the Module
>> classes I have created for now.
>>
>> Cheers,
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/cbea94ba-2216-4bae-be61-4456dd4e16ee%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/cbea94ba-2216-4bae-be61-4456dd4e16ee%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAPGcbtBz3aj717T%3D3Z%3D%3Dpq1zC8MpvE%3Dnz4DUcA5mU9YrP10Ejw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
