Log locations
Sections
The software distributed with PE generates log files you can use for troubleshooting.
Primary server logs
-
/var/log/puppetlabs/puppetserver/code-manager-access.log -
/var/log/puppetlabs/puppetserver/file-sync-access.log -
/var/log/puppetlabs/puppetserver/masterhttp.log -
/var/log/puppetlabs/puppetserver/pcp-broker.log— The log file for Puppet Communications Protocol brokers on compilers. -
/var/log/puppetlabs/puppetserver/puppetserver.log— The primary server logs its activity, including compilation errors and deprecation warnings, here. -
/var/log/puppetlabs/puppetserver/puppetserver-access.log -
/var/log/puppetlabs/puppetserver/puppetserver-daemon.log— This is where fatal errors or crash reports can be found. -
/var/log/puppetlabs/puppetserver/puppetserver-status.log
Agent logs
The locations of agent logs depend on the agent operating system.
On *nix nodes, the agent service logs its activity to
the syslog service. Your syslog configuration dictates where these messages are
saved, but the default location is /var/log/messages on Linux, /var/log/system.log on macOS, and /var/adm/messages on Solaris.
On Windows nodes, the agent service logs its activity to the event log. You can view its logs by browsing the event viewer.
Console and console services logs
-
/var/log/puppetlabs/console-services/console-services.log -
/var/log/puppetlabs/console-services/console-services-api-access.log -
/var/log/puppetlabs/console-services-access.log -
/var/log/puppetlabs/console-services-daemon.log— This is where fatal errors or crash reports can be found. -
/var/log/puppetlabs/nginx/access.log -
/var/log/puppetlabs/nginx/error.log— Contains errors related to nginx. Console errors that aren't logged elsewhere can be found in this log.
Installer logs
-
/var/log/puppetlabs/installer/http.log— Contains web requests sent to the installer. This log is present only on the machine from which a web-based installation was performed. -
/var/log/puppetlabs/installer/orchestrator_info.log— Contains run details aboutpuppet infrastructurecommands that use the orchestrator, including the commands to provision and upgrade compilers, convert legacy compilers, and regenerate agent and compiler certificates. -
/var/log/puppetlabs/installer/install_log.lastrun.<hostname>.log— Contains the contents of the last installer run. -
/var/log/puppetlabs/installer/installer-<timestamp>.log— Contains the operations performed and any errors that occurred during installation. -
/var/log/puppetlabs/installer/<action_name>_<timestamp>_<run_description>.log— Contains details about disaster recovery command execution. Each action triggers multiple Puppet runs, some on the primary server, some on the replica, so there might be multiple log files for each command.
Database logs
-
/var/log/puppetlabs/postgresql/9.6/pgstartup.log -
/var/log/puppetlabs/postgresql/9.6/postgresql-Mon.log -
/var/log/puppetlabs/postgresql/9.6/postgresql-Tue.log -
/var/log/puppetlabs/postgresql/9.6/postgresql-Wed.log -
/var/log/puppetlabs/postgresql/9.6/postgresql-Thu.log -
/var/log/puppetlabs/postgresql/9.6/postgresql-Fri.log -
/var/log/puppetlabs/postgresql/9.6/postgresql-Sat.log -
/var/log/puppetlabs/postgresql/9.6/postgresql-Sun.log -
/var/log/puppetlabs/puppetdb/puppetdb.log -
/var/log/puppetlabs/puppetdb/puppetdb-access.log -
/var/log/puppetlabs/puppetdb/puppetdb-status.log