Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

Please always provide us with both:

  1. atlassian-jira.log (see Logging and Profiling)
  2. the application server log file, as it can contain useful error information that is not in atlassian-jira.log

JIRA Log Location

The logs are written to the log subdirectory of your JIRA Home Directory (or elsewhere if you have configured a different location). You can view the location of the atlassian-jira.log in the 'File Paths' section of the System Information page.

Application Server Logs

Finding the application server log file is application server-specific and in some cases operating system-specific. Here is a decision tree:

  • If you are on Windows
    • ..and JIRA was installed as a Windows Service:
      • ..then the logs are in the logs\stdout_*.log file in your JIRA Installation Directory and c:\WINDOWS\system32\atlassian-jira.log (WINDOWS may be replaced by WINNT), or for JIRA WAR, in your Tomcat installation directory.
    • ..and JIRA was started via start-jira.bat:
      • ..then some logs are effectively being lost (to the popup DOS window, where it cannot be recaptured). Some logs do go to the atlassian-jira.log file in the current directory (wherever you ran startup.bat from) but this might not work if your current directory isn't writeable (eg. c:\WINNT\system32, the default). Even if you see an atlassian-jira.log it may be an old one, created from a previous startup. If you value your sanity (and ours) please install JIRA as a service, even if only to get all of the right logs appearing in a consistent place.
  • If you are on Linux or Solaris
    • ..then the logs are in logs/catalina.out in your JIRA Installation Directory, or for JIRA WAR, under your Tomcat installation directory.

2 Comments

  1. If you can't find your atlassian-jira.log and it's because you've edited the log4j.propeties file paths to include ${CATALINA.BASE} like any rational admin might do, please be advised I found this:

    JIRA has a new appender for logging to JIRA home. Customer who wants to customize the log file path, need to update the "log4j.appender.filelog=org.apache.log4j.RollingFileAppender". over at JRA-15256 - Could not find atlassian-jira.log Resolved

    So basically you need to replace their "com.atlassian.jira.logging.MultiTenantJiraHomeAppender" with standard "org.apache.log4j.RollingFileAppender" references. And if you're lucky enough to be attempting the WAR file configuration, you'll need to rebuild your war! Don't forget to copy that log4j.properties to the edit-webapp folder first!

    I'm also finding that you cannot run log4j at your container level if you're running WAR file Jira. There's issues related to sf4j.

  2. Anonymous