When you work with Support, we might ask you to generate a .yaml
file of a recent Puppet run for a node and attach it to a support ticket so that we can gain insight into managed resources and help you troubleshoot your deployment.
Version and installation information
PE version: All supported versions
OS: Any Unix
Installation type: Any
Solution
On the primary server:
-
In
/etc/puppetlabs/puppet/puppet.conf
, under[master]
edit thereports
setting to addstore
. For example:reports = puppetdb, store
. -
Restart Puppet Server.
puppet resource service pe-puppetserver ensure=stopped
puppet resource service pe-puppetserver ensure=running
-
Wait until Puppet has completed its next run. Navigate to
/opt/puppetlabs/server/data/puppetserver/reports
. Logs for each node are in directories named after the node's FQDN. -
Navigate to the directory of the node that you're troubleshooting. Find the most recent
.yaml
file. Attach the file to a support ticket. -
Prevent logs from filling your hard drive by turning off logging. Edit
/etc/puppetlabs/puppet/puppet.conf
to remove thestore
setting you added in step one. -
Restart Puppet Server.
puppet resource service pe-puppetserver ensure=stopped
puppet resource service pe-puppetserver ensure=running
How can we improve this article?
0 comments
Please sign in to leave a comment.
Related articles