On Friday, September 27, 2019 at 7:20:51 AM UTC-5, Dan Crisp wrote:
>
> Please see below. Apologies, there is a lot of detail here:
>
> Debug: Using settings: adding file resource 'confdir':
> 'File[/etc/puppetlabs/puppet]{:path=>"/etc/puppetlabs/puppet",
> :ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'
>
[...]
If the (elided) log messages presented were *all* the log messages emitted,
then they depict the agent applying an empty catalog, which is of course
consistent with not changing anything. All the resources shown are
generated locally by the agent. You should be able to confirm that by
looking at the catalog itself, which you will find, by default, in a file
in /opt/puppetlabs/puppet/cache/client_data/catalog.
If you're making changes to your manifest set but not seeing any effect at
the agent then there are several possibilities, but the most likely issue
is server-side caching. Before tweaking the cache configuration, however,
the easiest way to test this hypothesis is to flush the cache by restarting
the puppetserver service on the master. (That's not the only way, but it's
quick and easy, and you don't need to learn anything new to do it.)
If that indeed solves the problem then you'll want to adjust the
environment_timeout
<https://puppet.com/docs/puppet/latest/configuration.html#environmenttimeout>
configuration setting on the master. For the time being, I would suggest
setting it to 0 to disable caching altogether. This is also supposed to be
the default if the setting is not explicitly specified, however.
---
If that doesn't turn out to be the issue, then do have a look at the
master's logs. You should confirm that it is logging catalog requests from
the agent in question (else they must be going to a different master), and
you should look for any messages providing a clue about the issue. It may
be helpful to turn up puppetserver's log level to get more detailed
information.
If that's also unavailing then my last suggestion would be to confirm that
the puppetserver process can successfully access everything in the
environment directory. Check file ownership, mode, ACLs, SELinux context,
and anything else that affects whether the puppetserver can read the files
and traverse (all) the directories. I would pay special attention to your
one manifest file, because that's the most likely one to be messed up in
this regard.
John
--
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/bd705228-5459-43c6-9032-104dace92dee%40googlegroups.com.
