The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
https://tickets.puppetlabs.com. See the following page for information on filing tickets with JIRA:
Logdest cannot be set in the puppet.conf
|Assignee:||Charlie Sharpsteen||% Done:|
|Affected Puppet version:||Branch:|
This is potentially a duplicate issue of a few things floating around out there, but most focus on masterlog, so I’m opening this up separately. Currently you can use —logdest /var/log/somelogfile, but you cannot set it in the puppet.conf. This seems like an oversight, especially since there seems to be a good number of people who wish to keep all puppet logs out of /var/log/messages. There are ways around this (etc/init.d/pe-puppet), but they are purely workarounds. It looks like some of the reason for this is the old masterlog option, which it seems is no longer in use, used to be the preferred way of setting in the puppet.conf.
Potentially related tickets: https://projects.puppetlabs.com/issues/5952 https://projects.puppetlabs.com/issues/4550 https://projects.puppetlabs.com/issues/12361
#5 Updated by Anonymous over 2 years ago
- Tracker changed from Bug to Feature
The issue here is that logdest is not a setting, which would make it global to all subcommands and available to be set in puppet.conf. This isn’t really a bug, but a feature request to make logdest behave in a better manner. Not a big deal, but a slight clarification.
#8 Updated by Eddie Satterly over 1 year ago
A Splunk app has no way of checking if the service is logging where it is supposed to be and there are just no entries, or if the service has started with a certain cmd line switch easily. In the case of a config file that is out of the box for us as we use .conf files as well so we could check state and verify if in failure condition or just no activity. Otherwise we would have to do custom command for ps-ef with grep for service invocation and parse for cmd line switch and that is ugly and prone to issues, especially with version changes.