Permission Denied during JIRA Setup Wizard
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
Failure to complete initial setup of JIRA using the Setup Wizard
The following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
2014-08-05 12:14:29,086 http-bio-8080-exec-9 ERROR anonymous 733x6x1 480rvw 172.20.65.212 /secure/SetupDatabase.jspa [jira.bc.dataimport.DefaultDataImportService] Error importing data: java.lang.IllegalStateException: java.io.IOException: Permission denied
java.lang.IllegalStateException: java.io.IOException: Permission denied
at net.java.ao.db.FileSystemUtils$1.get(FileSystemUtils.java:43)
at net.java.ao.db.FileSystemUtils$1.get(FileSystemUtils.java:24)
at com.google.common.base.Suppliers$MemoizingSupplier.get(Suppliers.java:109)
at net.java.ao.db.FileSystemUtils.isCaseSensitive(FileSystemUtils.java:50)
at net.java.ao.db.MySQLDatabaseProvider.isCaseSensitive(MySQLDatabaseProvider.java:156)
at net.java.ao.schema.helper.DatabaseMetaDataReaderImpl.getTableNames(DatabaseMetaDataReaderImpl.java:58)
at net.java.ao.schema.ddl.SchemaReader.readSchema(SchemaReader.java:106)
at net.java.ao.schema.ddl.SchemaReader.readSchema(SchemaReader.java:94)
at net.java.ao.schema.ddl.SchemaReader.readSchema(SchemaReader.java:85)
at com.atlassian.activeobjects.backup.ActiveObjectsDatabaseCleaner.doCleanup(ActiveObjectsDatabaseCleaner.java:61)
at com.atlassian.activeobjects.backup.ActiveObjectsDatabaseCleaner.cleanup(ActiveObjectsDatabaseCleaner.java:46)
Caused by: java.io.IOException: Permission denied
at java.io.UnixFileSystem.createFileExclusively(Native Method)Cause
Filesystem level permissions are preventing JIRA from writing to disk.
Check the context labels if you're using Podman volumes and SELinux
Resolution
Ensure that the user running the application has read/write permissions to both <jira-home> and <jira-install> directories recursively. You could follow the resolution steps from Actions in Jira server fails with FileNotFoundException in the Jira logs.
Was this helpful?