When an issue is preventing nodes from checking in (they have become unresponsive), you can generate a list of the affected node’s certnames to troubleshoot the issue. You can generate a list of unresponsive nodes by running a PQL query or checking the Status page in the console.
Version and installation information
PE version: All supported
Solution
Generate a list of unresponsive node certnames using PQL
You can check which nodes are unresponsive on any infrastructure node or any node with client tools installed, In the CLI, run:
puppet query 'nodes[certname,latest_report_status,report_timestamp]{report_timestamp<"<AN HOUR AGO>"}'
For example:
puppet query 'nodes[certname,latest_report_status,report_timestamp]{report_timestamp<"2022-09-22T11:06:26.140Z"}'
Output is similar to the following:
{
"certname": "pe-server-245b79-0.us-west1-a.c.customer-support-scratchpad.internal",
"latest_report_status": "failed",
"report_timestamp": "2022-09-23T08:05:19.676Z"
},
{
"certname": "pe-node-245b79-0.us-west1-a.c.customer-support-scratchpad.internal",
"latest_report_status": "unchanged",
"report_timestamp": "2022-09-23T10:33:14.660Z"
},
By default, Puppet automatically attempts to run on each of your nodes every 30 minutes. If you’ve set a different interval for Puppet runs, adjust the amount of time in the query.
Generate a list of unresponsive node certnames in the console
In the console, the Status page displays the most recent run status of each of your nodes. Nodes that have not checked in recently are listed as Unresponsive. To export the data as a .csv
, click Export data. The default for considering a node unresponsive is one hour. You can configure it via the puppet_enterprise::console_services::no_longer_reporting_cutoff
parameter. See Configure the PE console and console-services for more information. As you’re troubleshooting, you can also run Puppet from the console to help you resolve the issue.
Next steps
For more insight on unresponsive nodes, read Agent nodes are unresponsive (not reporting) in the console in Puppet Enterprise.
If you’re not able to solve this issue, please open a ticket.
How can we improve this article?
0 comments
Please sign in to leave a comment.
Related articles