Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-2997

Logdest cannot be set in the puppet.conf

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • PUP 3.8.7, PUP 4.8.1, PUP 4.10.10, PUP 5.5.0
    • PUP 5.5.7, PUP 6.0.3
    • None
    • Normal
    • 2 - 5-25% of Customers
    • 3 - Serious
    • 4 - $$$$$
    • Hide
      Users sometimes want to send their logs to a different location and have this work for ALL invocations of puppet(daemon or CLI). Example cases mentioned in this ticket are to send everything to splunk, or to make the puppet logs available to less privileged users. The wrapper script that was added in Puppet 5 could be modified to source a logdest from some other file such as puppet.conf or if that isn't workable something like environment settings such as sysconfig
      Show
      Users sometimes want to send their logs to a different location and have this work for ALL invocations of puppet(daemon or CLI). Example cases mentioned in this ticket are to send everything to splunk, or to make the puppet logs available to less privileged users. The wrapper script that was added in Puppet 5 could be modified to source a logdest from some other file such as puppet.conf or if that isn't workable something like environment settings such as sysconfig
    • 34390
    • 1
    • New Feature
    • The `--logdest` argument can now also be set in the puppet.conf file as the `logdest` setting.

    Description

      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

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. PUP-2989 3.x "profile = true" and "--profile" does nothing.

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PUP-5068 Windows - Allow logging to a different event log

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          [Puppet Labs Redmine] Redmine (#4761) Allow verbose and debug options to be specified in configuration file in addition to command line

          [Puppet Labs Redmine] Redmine (#5952) Fix logdir, logdest and other disaster options

          [Puppet Labs Redmine] Redmine (#12361) "masterlog" option does not appear to be used

          clones

          [Puppet Labs Redmine] Redmine (#20173) Logdest cannot be set in the puppet.conf

          mentioned in

          Page Loading...

          Page Loading...

          Activity

            People

              jacob.helwig Jacob Helwig
              redmine.exporter redmine.exporter
              Votes:
              6 Vote for this issue
              Watchers:
              19 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support