JIRA log file paths are always rooted under JIRA_HOME if set

XMLWordPrintable

    • 4.01
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 16 November 2017

      Hi everyone,

      The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low.
      Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out.

      Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments.

      Cheers,
      Ignat Alexeyenko
      Jira bugmaster.

      Show
      Atlassian Update – 16 November 2017 Hi everyone, The issue has not collected enough votes, watches, comments or support cases during it's lifetime. In this sense overal interest in the reported problem is low. Jira team is focusing on bigger and more impactful issues at the moment and we are not likely to look at the current bug soon. Therefore I'm resolving the issue as Timed Out . Atlassian will continue to watch issue for the further updates, so please don't hesitate to share your feedback in the issue comments. Cheers, Ignat Alexeyenko Jira bugmaster.

      When JIRA_HOME is set, all log file paths are rooted under JIRA_HOME/log, even when an absolute path is set for the log file path in log4j.properties. For instance, JIRA_HOME is set to /data/jira and the path to the atlassian-jira log file is set to /data/jira/logs/atlassian-jira.log in log4j.properties. The log file ends up in /data/jira/log/data/jira/logs/atlassian-jira.log when it should actually be in /data/jira/logs/atlassian-jira.log.

              Assignee:
              Unassigned
              Reporter:
              Jeremy Bopp
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: