Problem Definition

In some cases Jira is not able to run properly due to file or directory permission error, this is usually caused by running Jira services as a different user before the normal run.
Having full write access to the <Jira_Home> and some folders in the <Jira_Install> are required for normal operations

Example of errors:

• Example1

  2020-09-28 22:25:16,090+0000 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger] 
      
      ****************
      Jira starting...
      ****************
      
  log4j:ERROR setFile(null,true) call failed.
  java.io.FileNotFoundException: /disk/data/atlassian/application-data/jira/log/atlassian-jira.log (Permission denied)
  	at java.io.FileOutputStream.open0(Native Method)
  	at java.io.FileOutputStream.open(FileOutputStream.java:270)
  	...
  

• Example2

  2020-09-28 22:25:32,838+0000 JIRA-Bootstrap ERROR      [c.a.jira.startup.ComponentContainerLauncher] A fatal error occurred during initialisation. JIRA has been locked.
  com.atlassian.plugin.osgi.container.OsgiContainerException: Unable to clean the cache directory: /disk/data/atlassian/application-data/jira/plugins/.osgi-plugins/felix
  	at com.atlassian.plugin.osgi.container.impl.DefaultOsgiPersistentCache.validate(DefaultOsgiPersistentCache.java:71)
  	...
  Caused by: java.io.IOException: Failed to list contents of /disk/data/atlassian/application-data/jira/plugins/.osgi-plugins/felix
  

See also related KB How to fix directory permissions in Linux for Jira Server

Suggested Solution

• Add a file system permission to validate permission before starting the Tomcat/Java

Workaround

None