Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira not auto starting on CentOS7

Rob Reidy
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 6, 2019

Installed Jira Software version 8.2.1 on CentOS 7.6.1810 with latest PostgreSQL. Ran the installer with sudo. Created jira:jira user/group. It was working until a reboot. Followed steps at below link to set it to auto start, but it doesn't work.

(Skipped steps 2,3,4 since it was alread installed.)
https://confluence.atlassian.com/jirakb/starting-jira-automatically-on-linux-828796713.html

I only edited these 2 variable values accordingly.

# Location of application's bin directory
BASE=/opt/atlassian/jira
# Location of Java JDK
export JAVA_HOME=/usr/bin/java

 

"service jira start" works as root, jira, and other users. It just doesn't auto-start on boot. I assume the above values are correct since the start|stop commands work.

$ chkconfig --list jira

Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.

If you want to list systemd services use 'systemctl list-unit-files'.
To see services enabled on particular target use
'systemctl list-dependencies [target]'.

jira 0:off 1:off 2:off 3:on 4:off 5:on 6:off

 

Not sure what the "masked" is about. I get it regardless of which user I send the command as.

$ systemctl list-unit-files | grep jira
jira.service masked

 

I also did chown -R jira /opt/atlassian/jira/, but it made no difference. Should I chown these back to root?

BTW, the documentation for installing on CentOS with PostgreSQL (the recommended platforms) is unforgivably sloppy/disjointed/missing critical steps. I went out of my way to research what is officially recommended and complying has been insane. Like, it says to use MySQL as your DB when installing on CentOS, with no further explanation. Default install of MySQL results in MariaDB, which is "not supported". It's like this all over the place. It has been a 20+ hour nightmare just to get Jira up. Now another 4+ to get the auto-start working. I'm sure my current problem is a result of these bad instructions.

 

1 answer

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 10, 2019

Hi Rob,

Sorry to hear about this problem.  I understand that you are walking through an installation of Jira on a CentOS machine and having troubles getting Jira to start up as a service.  I'm afraid that the KB you are referencing there was created a while back for much older versions of Linux that handled services a bit differently than the more modern Linux distros do today.  And in turn there have been some changes to CentOS 7 in regards to using chkconfig. 

We have a bug about this problem in JRASERVER-42000.  That bug focuses on getting the installer to correctly set this up.

In the meantime, there are some alternative ways to set this up.  Check out Daniel's answer over in https://community.atlassian.com/t5/Jira-questions/Run-jira-as-a-service-in-linux/qaq-p/876850

I think this will help in this case.

I will look into updating that KB you referenced to try to help other users that might run across this.  

I would also be interested to know what specific guide you were following when trying to install Jira.  I'm surprised to hear you state that MySQL was a recommended platform for Jira.  In my experience that hasn't been the case so I'm curious to know where in our documentation it states that.

Thanks

Andy

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events