Table of contents
This page describes what to do in case of an Icinga alert. For more information you could search the govuk-puppet repo for the source of the alert

Puppet last run errors

This alert triggers when there’s an error while running Puppet on a machine.

To view the errors in Kibana, first login to Logit, and then run the following query (where $hostname is the short name of the machine linked to the alert, for example backend-1):

syslog_program:"puppet-agent" AND host:$hostname

You may also SSH into the machine and look at syslog:

tail /var/log/syslog

You can also try running Puppet again and check the output:

govuk_puppet --test

Sometimes this alert means that there is a puppet lock on the machine, so puppet won’t be run. You can list current locks by running:

govuk_puppet -l

Could not parse puppet summary file

This usually means the Puppet client is unable to retrieve the catalogue from the master.

The file that the check uses is /var/lib/puppet/state/last_run_summary.yaml. If it is only a few lines long, check logs for the error as above.

More about Icinga alerts

This page was last reviewed . It needs to be reviewed again by the page owner #govuk-2ndline.