Database
- Puppet Server fails after “pg_wal” fills up the hard drive in Puppet Enterprise
- Prevent PuppetDB from failing after Puppet Enterprise upgrade on an external unmanaged PostgreSQL node
- PQL query to return all nodes where a fact does not exist in Puppet Enterprise
- Efficiently run a PQL query on a long list of nodes in Puppet Enterprise
- Determine if large facts cause performance issues in Puppet Enterprise
- Monitor the performance of your Puppet Enterprise infrastructure
- After a Disaster Recovery failover in Puppet Enterprise, PuppetDB is unresponsive
- "Address already in use" error when starting PuppetDB service
- Use tasks to run PuppetDB and PostgreSQL commands in the console in Puppet Enterprise 2018.1 and later
- Removing nodes: Understanding "puppet node purge", "node-ttl", and "node-purge-ttl" in Puppet Enterprise 2019.4 and later
- After upgrading to Puppet Enterprise 2019.8.3 or 2019.8.4, PuppetDB restarts after agent logs “facts_blacklist is deprecated” or “cert_whitelist_path is deprecated” errors
- Timeout error connecting to PuppetDB in the Puppet Enterprise 2019.8.4 console
- Compilers converted to run PuppetDB relying on high-latency connections experience slowdowns in Puppet Enterprise 2019.8
- Troubleshoot PuppetDB (pe-puppetdb) in Puppet Enterprise
- Change the PuppetDB port in Puppet Enterprise
- Learn to use Puppet Query Language (PQL)
- Check database table sizes in Puppet Enterprise
- PostgreSQL logs filling up in Puppet Enterprise 2018.1.0
- REST API call to PuppetDB with PowerShell "Invoke-RestMethod" command returns a "The underlying connection was closed" error in Puppet Enterprise
- Resolve a 'PuppetDB: Connection refused' error in Puppet Enterprise
- Recommended reading - Performing complex searches on Package Inspector data for Puppet Enterprise
- Removing nodes: Understanding "puppet node purge", "node-ttl", and "node-purge-ttl" in Puppet Enterprise 2015.2 to 2019.2