Puppet runs fail with a "WARNING: MSG:UnableToDownload" on Windows 2016 and earlier when using Chocolately
Ensure that fact-based classification and automation work as expected by uploading facts to the master in Puppet Enterprise 2018.1 and later
Agent runs fail on a FIPS enabled master in Puppet Enterprise 2018.1 to 2019.1
"Pe_repo" error during Puppet runs after installing Bolt on a Puppet Enterprise master
After a Red Hat 7 OS update agents are not responding in the console in Puppet Enterprise
"no implicit conversion from nil to integer" error in Puppet Enterprise 2018.1.x
Puppet agent runs fail with a "Could not find catalog" error in Puppet Enterprise 2018.1.3
Use a task to enable or disable the Puppet daemon for a group of agents in Puppet Enterprise 2018.x
Identifying nodes where the Puppet daemon is enabled or disabled in Puppet Enterprise 2017.3.x to 2019.2.x
Troubleshooting agent run errors and slow runs in Puppet Enterprise by adding flags

See more

Change the agent logging location using "--logdest" for Puppet Enterprise 2015.x to 2017.3.x

Gareth McGrillan

May 18, 2020 23:38
Updated

Did this solve your problem?

0 out of 0 found this helpful

Global system messages and agent runs both log to /var/log/messages/ by default. It is hard for me to find critical system messages in the log. I can change the logging location with syslog, but I ...

Read this full article with Puppet Support

Sign in to your account Learn more about Puppet products

Can't sign in? Get help

Comments

0 comments

Please sign in to leave a comment.