Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,816
Community Members
 
Community Events
176
Community Groups

CentOS 7 / systemd startup scripts for Jira & Fisheye

JIRA / Fisheye have handy startup scripts for SysV here: https://confluence.atlassian.com/display/FISHKB/How+to+start+FishEye+and+Crucible+at+boot+time+on+Linux

Are there any service scripts like that available for CentOS/RHEL 7, or systemd in general as it seems many distributions are migrating to it?

3 answers

Hi,

try these steps on CentOS 7.x:

 

1) Install and configure jsou JIRA instance (user under JIRA will run under, JIRA_HOME etc.)

2) Create file with service config

sudo vi /usr/lib/systemd/system/jira.service

3) Your jira.service file should contain something like this:

[Unit]
Description=JIRA Service
After=network.target iptables.service firewalld.service firewalld.service httpd.service

[Service]
Type=forking
User=jira
Environment=JRE_HOME=/usr/java/jdk1.8.0_74
ExecStart=/opt/jira710/bin/start-jira.sh
ExecStop=/opt/jira710/bin/stop-jira.sh
ExecReload=/opt/jira710/bin/stop-jira.sh | sleep 60 | /opt/jira710/bin/start-jira.sh

[Install]

WantedBy=multi-user.target

Please notice that the paths to JIRA scripts and JAVA_HOME need to be changed to right one on your server smile. Also you may need to update the parameter named After - regarding to your server services (e.g. if you do not have JIRA Tomcat behind the reverse proxy (http), remove http.service. If your JIRA needs to wait for a DB start, add the DB service here, e.g. mariadb.service or mysqld.service etc.).

4) Run

sudo systemctl daemon-reload

5) Start JIRA:

sudo systemctl start jira

6) If you want to start JIRA automatically when OS starts:

sudo systemctl enable jira

 

Vitek

Thanks Vitek, that is the best answer!

thanks. I think http.service must be started after JIRA service, not before. 

Saved my day six years later.

If using mariadb / mysql as the database system, change your jira.service file so that JIRA waits for MariaDB to start up first:

[Unit]
Description=JIRA Service
After=network.target iptables.service firewalld.service firewalld.service httpd.service mariadb.service

 

 

0 votes

I am not certain, but have you tried installing JIRA via the binary installer? It detects and installs the right startup scripts normally. Not entirely sure that is the case for systemd but worth a try. You could do this in a VM, and then pull the scripts out for your prod environment if they work as expected.

I just installed JIRA 6.3.15 from the binary installer, doesn't have systemd scripts, just SysV service scripts. Since RedHat/CentOS/Fedora/openSUSE/Debian/Ubuntu have all migrated to systemd figured someone would have created some scripts to run on boot for it by now

Screenshot 2015-02-09 17.09.31.png

 

Did you test this on a CentOS system? Try Ubuntu, we may just be pushing the SysV scripts when we should be deploying systemd ones.

yes this was on a fully patched CentOS 7 system, I don't have any Ubuntu servers at the moment

I don't think that there are any systemd scripts just as you outlined. I have filed a bug about this issue at: https://jira.atlassian.com/browse/JRA-42000

Suggest an answer

Log in or Sign up to answer