To stop/start JIRA in Linux environment, which Linux user should be used ? Is it user "jira" or user "root". Starting/stopping jira as "root" user cause any kind of issues ?

Please advise. Thanks

4 answers

1 accepted

2 votes
Accepted answer

Since Jira 6, the startup process has been improved. If you installed Jira as root using the install wizard, it should have created a new "jira" user for you, as well as set up Jira as a service which will run automatically on startup. If you run /etc/init.d/jira {stop|start} as root, the script will drop itself to run as the "jira" user before starting the application.

It looks like 5.2 also creates a jira user, if the installer was run as root:
(see note at the end of step 1)

If you're unsure, you can run the and scripts as the jira user, to be safe. These are in the bin directory of your Jira installation.

Step 4 of the above link also has instructions for setting up Jira to run as a service, if you didn't run the installer as root.


do you have the init script installed?

if i am not totally wrong then the user jira is set inside there...

so this is the reason you can start jira using "/etc/init.d/jira start" as root user and the process owner will be user "jira"

as renjith already stated it is not recommended to run any service as root user. stick with the one your installer created for you and it should be fine.

jira version which we are using : 5.2.7


Running JIRA under root user is never recommeded. It is always safe to run JIRA under the limited user 'jira' which is taken care automatically, as Andrew says, if the installer was used.


Even if start jira as root user in Linux. The owner of the process remains "jira". How does it cause issue ? Details below. Sorry, I am trying to understand.

ps -eaf | grep -i jira

jira 11786 1 4 Jul12 ? 12:25:08 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/ -XX:MaxPermSize=256m -Xms768m -Xmx4096m -Djava.awt.headless=true -Datlassian.standalone=JIRA -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true -Dmail.mime.decodeparameters=true -XX:+PrintGCDateStamps -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/opt/atlassian/jira/endorsed -classpath /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/jira -Dcatalina.home=/opt/atlassian/jira org.apache.catalina.startup.Bootstrap start


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,737 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you