Error installing JIRA on Debian

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

Problem

When installing JIRA on a Debian server, the following exception is thrown:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 Extracting files ... com.install4j.runtime.beans.actions.misc.RunExecutableAction failed Ignore [i, Enter], Quit [q] i Please wait a few moments while JIRA starts up. Launching JIRA ... Installation of JIRA 6.4.13 is complete Your installation of JIRA 6.4.13 is now ready and can be accessed via your browser. JIRA 6.4.13 can be accessed at http://localhost:8088 In action "Write Modz Registry [Run script]" (screen "Custom Finish Screen [Configurable banner form]"), property "Script": java.lang.IllegalArgumentException: appBaseDir '/atlassian-jira' is not a readable directory at com.atlassian.inception.modz.ModificationHelper.checkReadableDir(ModificationHelper.java:219) at com.atlassian.inception.modz.ModificationHelper.<init>(ModificationHelper.java:68) at com.atlassian.inception.modz.JiraModificationHelper.<init>(JiraModificationHelper.java:18) at com.atlassian.inception.modz.ModificationHelper.createJiraHelper(ModificationHelper.java:60) at I4jScript_Internal_424.eval(I4jScript_Internal_424.java:24) at I4jScript_Internal_424.evaluate(I4jScript_Internal_424.java:33) at com.install4j.runtime.installer.helper.Script.evaluate(Unknown Source) at com.install4j.runtime.installer.ContextImpl.runScript(Unknown Source) at com.install4j.runtime.installer.ContextImpl.runScript(Unknown Source) at com.install4j.runtime.beans.actions.control.RunScriptAction.execute(Unknown Source) at com.install4j.runtime.beans.actions.SystemInstallOrUninstallAction.install(Unknown Source) at com.install4j.runtime.installer.InstallerContextImpl.performActionInt(Unknown Source) at com.install4j.runtime.installer.ContextImpl.performAction(Unknown Source) at com.install4j.runtime.installer.controller.Controller.executeActions(Unknown Source) at com.install4j.runtime.installer.controller.Controller.handleCommand(Unknown Source) at com.install4j.runtime.installer.controller.Controller.start(Unknown Source) at com.install4j.runtime.installer.Installer.main(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.exe4j.runtime.LauncherEngine.launch(Unknown Source) at com.install4j.runtime.launcher.Launcher.main(Unknown Source) Unable to register filesystem for installer modification checking. Finishing installation ..

Cause

Debian does not have /opt directory by default.

Resolution

Create the /opt directory manually at the root level and re-run the installation.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.