Skip to content

Instantly share code, notes, and snippets.

@tkishel

tkishel/agent_not_reporting.md

Last active March 25, 2020 23:43
Show Gist options
  • Save tkishel/994817bbf91e411834550004fa022d43 to your computer and use it in GitHub Desktop.
Save tkishel/994817bbf91e411834550004fa022d43 to your computer and use it in GitHub Desktop.
Download ZIP
Decision Tree: Agent Not Reporting in the Console
Raw
agent_not_reporting.md

Decision Tree: Agent Not Reporting in Console on Master

  • Verify the server setting in puppet.conf on the Agent is set to the Master (or the Load Balancer of the Master).

  • Verify that the Puppet Agent service is running on the Agent.

    • If it not running, review the Application and System logs.
      • If you find a correlated "Puppet Agent service entered the stopped state" event ...
        • A process or a user explicitly stopped the service.
          • Look for the process or user that stopped the service.
      • If you find a correlated "Puppet Agent service terminated unexpectedly" event ...
        • The service crashed.
          • Look for errors prior to that crash for a root cause.
      • Start the Puppet Service on the Agent.
        • Review the Application and System logs.
          • Verify the service remains started.
          • Verify the service initiates a puppet agent run immediately after starting.
          • Verify that run completes successfully.

  • Verify that a puppet agent run is not zombied on the Agent.

    • If it is (Puppet Agent service is running, puppet agent run remains in progress for more than runinterval) ...
      • Review the timestamps of files in C:\ProgramData\PuppetLabs\puppet\cache
        • Verify the start time of the last run.
      • Review the Application and System logs.
        • Look for the start time of the last run, and for errors before and during that run for a root cause.
          • If you find errors communicating with the Master ...
            • Review the logs on the Load Balancer, Compiler, and the Master for a root cause.
      • Verify the runtimeout setting in puppet.conf on the Agent is set to less than runinterval (for example runtimeout=20, runinterval=30) but more than the default of 0 (no timeout).
      • Stop and start the Puppet Agent service to kill the run.
        • Review the Application and System logs.
          • Verify the service remains started.
          • Verify the service kills the run.
            • If it does not kill the run ...
              • Kill it manually, and delete its lockfile.
              • Stop and start the Puppet Agent service.
              • Verify the service remains started.
          • Verify the service initiates a puppet agent run immediately after starting.
          • Verify that run completes successfully.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment