Startup check: Starting JIRA
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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
Purpose
How you start and stop your JIRA application depends on whether you are running JIRA as a Service.
Windows
Installed as a Service
If you installed JIRA as a service (default option using the installer), you can Start JIRA Server and Stop JIRA Server from the Windows Start menu.
You can't start or stop JIRA manually using the start-jira.bat
and stop-jira.bat
file.
Manual Start
If you didn't install JIRA as a service you'll need to start and stop JIRA manually.
- To start JIRA run
<installation-directory>\bin\start-jira.bat
- To stop JIRA run
<installation-directory>\bin\stop-jira.bat
We recommend running JIRA with a dedicated user account. To do this, use usethe runas
command to execute start-jira.bat
.
> runas /env /user:<DOMAIN>\<jira> start-jira.bat
Where <DOMAIN>
is your Windows domain or computer name and <jira>
is the name of your dedicated user.
Linux
Installed as a Service
If you installed JIRA as a service, use one of the following commands to start or stop JIRA.
$ sudo /etc/init.d/jira start
$ sudo /etc/init.d/jira stop
You can't start or stop JIRA manually using the start-jira.sh
and stop-jira.sh
files.
Manual Start
If you didn't install JIRA as a service you'll need to start and stop JIRA manually.
- To start JIRA run
<installation-directory>\bin\start-jira.sh
- To stop JIRA run
<installation-directory>\bin\stop-jira.sh
We recommend running JIRA with a dedicated user account:
$ su -u <user>
$ ./start-jira.sh
Where <user>
is the name of your dedicated user. If you're using Ubuntu the command is a little different:
$ sudo su <user>
$ ./start-jira.sh
Disabling plugins on Jira startup
Starting from JIRA 7.3, you can start JIRA with all non-system add-ons, or a selection of these add-ons, disabled. This helps with troubleshooting when these non-system add-ons are causing issues with your JIRA instance, such as causing JIRA to fail on start up, or when the add-on is malfunctioning and can't be removed through UPM. There are two ways to set them, depending on the startup method:
Manual Start
When JIRA is started using the start-jira.bat or start-jira.sh, the following parameters should be specified at system startup to disable all plugins:
WINDOWS
<installation-directory>/bin/start-jira.bat /disablealladdons
LINUX
<installation-directory>/bin/start-jira.sh --disable-all-addons
To disable only specific plugins, use a colon-separated list of plugins. Regex/wildcards are not permitted, the full key of the plugin must be provided, for example:
WINDOWS
<installation-directory>/bin/start-jira.bat /disableaddons=com.atlassian.test.plugin:com.atlassian.another.test.plugin
LINUX
<installation-directory>/bin/start-jira.sh --disable-addons=com.atlassian.test.plugin:com.atlassian.another.test.plugin
These parameters do not persist, that is, they are applied at startup once, and if you need to restart JIRA, you need to apply them again.
JVM Parameter
If you don't use start-jira.bat or start-jira.sh for starting JIRA, but still wish to use this feature, you can add the following JVM parameters to the invocation of the servlet container that's running JIRA, these will persist upon restarting the application. Here we have both:
WINDOWS
-Datlassian.plugins.startup.options="/disablealladdons"
LINUX
-Datlassian.plugins.startup.options="--disable-all-addons"
WINDOWS
-Datlassian.plugins.startup.options="/disableaddons=com.atlassian.test.plugin:com.atlassian.another.test.plugin"
LINUX
-Datlassian.plugins.startup.options="--disable-addons=com.atlassian.test.plugin:com.atlassian.another.test.plugin"
Starting Jira Datacenter without apps
As the above-mentioned "--disable-all-addons" parameters don't work for the Jira datacenter please try to manually rename the installed-plugins folder under Jira shared home to start Jira DC without apps
- Stop JIRA
- Go to your the $JIRA-Shared-Home/plugins/installed-plugins directory
- Rename the $JIRA-Shared-Home/plugins/installed-plugins directory to $JIRA--Shared-Home/plugins/installed-plugins2
- Restart Jira - This will re-create the $JIRA-Home/plugins/installed-plugins directory but Jira will start without any apps
- If the issue is no longer reproducible, Reinstall the apps with the latest version through the Administration > Add-ons > Find new apps page.
- You may later delete the $JIRA-Shared-Home/plugins/installed-plugins2 directory which is no longer in use.
Notes
- This feature does not work for JIRA Data Center applications.
- disable-addons parameter takes a colon-separated list (chosen as a colon is the only prohibited character from a plugin key) of add-ons to be disabled. These can be system add-ons.
- If the add-on key contains a space, this feature will not work, you need to manually deal with that add-on.
This can be used to disable an add-on deemed critical to JIRA starting, and if one of those is disabled, JIRA will fail to start.
This can be used to disable JIRA application OBR bundles, for example, to stop the JIRA Software add-on:
WINDOWS <installation-directory>/bin/start-jira.bat /disableaddons=com.atlassian.jira.jira-software-application LINUX <installation-directory>/bin/start-jira.sh --disable-addons=com.atlassian.jira.jira-software-application