Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-95

INI config parsing failures will get swallowed by default

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: PDB 1.5.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Story Points:
      2

      Description

      Currently log4j config information is put in our regular INI config file. There is a gap in time between JVM startup, with default log4j config and when the appender is changed via the INI file. If there is a problem parsing the INI file, the appender would not have been changed per the user config, and by default any error message would be written to standard out. Our current scripts redirect all standard out/error to /dev/null, swallowing all exception/error output.

      There are several ways to fix this problem. One is to redirect standard out/error to files, rather than /dev/null. Another would be to include a default log4j.properties to point to some common default log location.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            redmine.exporter redmine.exporter
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support