Capture a .yaml file of a Puppet run for Puppet Enterprise

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 (called the master in versions of PE earlier than 2019.8):

1. In /etc/puppetlabs/puppet/puppet.conf, under [master] edit the reports setting to add store. For example: reports = puppetdb, store.

2. Restart Puppet Server.

   • puppet resource service pe-puppetserver ensure=stopped
   • puppet resource service pe-puppetserver ensure=running

3. 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.

4. Navigate to the directory of the node that you're troubleshooting. Find the most recent .yaml file. Attach the file to a support ticket.

5. Prevent logs from filling your hard drive by turning off logging. Edit /etc/puppetlabs/puppet/puppet.conf to remove the store setting you added in step one.

6. Restart Puppet Server.

   • puppet resource service pe-puppetserver ensure=stopped
   • puppet resource service pe-puppetserver ensure=running