How do we configure Systemd startup script on Centos7 ?

[Theodore Knab]

Problem: Systemd startup script on Centos7 is not start/restarting jira. But manuals starts using the "start-jira.sh" script work. How do I fix the startup script ?

Manual runs with the following seem to work:

/var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/bin/start-jira.sh -fg
/var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/bin/start-jira.sh
/var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/bin/stop-jira.sh

Possible related:
https://confluence.atlassian.com/jirakb/run-jira-as-a-systemd-service-on-linux-979411854.html
https://jira.atlassian.com/browse/JRASERVER-42000

[root@ljira1d ~]# systemctl status jira
● jira.service - Atlassian Systemd Jira Service
Loaded: loaded (/usr/lib/systemd/system/jira.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2020-08-28 08:04:26 EDT; 4s ago
Process: 43583 ExecStart=/var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/bin/start-jira.sh (code=exited, status=0/SUCCESS)
Main PID: 43608 (code=exited, status=126)

Aug 28 08:04:26 ljira1d.example.net start-jira.sh[43583]: Version : 8.8.1
Aug 28 08:04:26 ljira1d.example.net start-jira.sh[43583]: If you encounter issues starting or stopping JIRA, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide
Aug 28 08:04:26 ljira1d.example.net start-jira.sh[43583]: Using JIRA_HOME: /var/atlassian/application-data/jira-home
Aug 28 08:04:26 ljira1d.example.net start-jira.sh[43583]: Server startup logs are located in /var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/logs/catalina.out
Aug 28 08:04:26 ljira1d.example.net start-jira.sh[43583]: /var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/bin/check-java.sh: line 31: [: -ne: unary operator expected
Aug 28 08:04:26 ljira1d.example.net start-jira.sh[43583]: /var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/bin/set-gc-params.sh: line 5: [: -ge: unary operator expected
Aug 28 08:04:26 ljira1d.example.net systemd[1]: Started Atlassian Systemd Jira Service.
Aug 28 08:04:26 ljira1d.example.net systemd[1]: jira.service: main process exited, code=exited, status=126/n/a
Aug 28 08:04:26 ljira1d.example.net systemd[1]: Unit jira.service entered failed state.
Aug 28 08:04:26 ljira1d.example.net systemd[1]: jira.service failed.

The startup file looks like this:

[root@ljira1d ~]# cat /usr/lib/systemd/system/jira.service
[Unit]
Description=Atlassian Systemd Jira Service
After=syslog.target network.target

[Service]
Type=forking
PIDFile=/var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/work/catalina.pid
Environment="JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.201.b09-2.el7_6.x86_64/jre/bin/java"
User=jira
ExecStart=/var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/bin/start-jira.sh
ExecStop=/var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/bin/stop-jira.sh

[Install]
WantedBy=multi-user.target

I see this in the logs when trying to start the service:

-- Unit jira.service has begun starting up.
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: To run Jira in the foreground, start the server with start-jira.sh -fg
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: executing as current user
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: `sMMMMMMMMMMMMMM+
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: MMMMMMMMMMMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: :sdMMMMMMMMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: MMMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: `sMMMMMMMMMMMMMM+ MMMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: MMMMMMMMMMMMMM +MMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: :sMMMMMMMMMMM MMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: MMMMMM `UOJ
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: `sMMMMMMMMMMMMM+ MMMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: MMMMMMMMMMMMMM +MMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: :sdMMMMMMMMMM MMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: MMMMMM `UOJ
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: MMMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: +MMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: MMMMM
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: `UOJ
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: Atlassian Jira
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: Version : 8.8.1
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: If you encounter issues starting or stopping JIRA, please see the Troubleshooting guide at http://confluence.atlassian.com/display/JIRA/Installation+Troubleshooting+Guide
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: Using JIRA_HOME: /var/atlassian/application-data/jira-home
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: Server startup logs are located in /var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/logs/catalina.out
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: /var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/bin/check-java.sh: line 31: [: -ne: unary operator expected
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: /var/atlassian/atlassian-jira/atlassian-jira-software-8.8.1-standalone/bin/set-gc-params.sh: line 5: [: -ge: unary operator expected
Aug 28 08:20:10 ljira1d.example.net start-jira.sh[44726]: Tomcat started.
Aug 28 08:20:10 ljira1d.example.net polkitd[659]: Unregistered Authentication Agent for unix-process:44720:198876689 (system bus name :1.28440, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
Aug 28 08:20:10 ljira1d.example.net systemd[1]: Started Atlassian Systemd Jira Service.
-- Subject: Unit jira.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit jira.service has finished starting up.
--
-- The start-up result is done.
Aug 28 08:20:10 ljira1d.example.net systemd[1]: jira.service: main process exited, code=exited, status=126/n/a
Aug 28 08:20:10 ljira1d.example.net systemd[1]: Unit jira.service entered failed state.
Aug 28 08:20:10 ljira1d.example.net systemd[1]: jira.service failed.

[Theodore Knab]

I solved this one.

Fix edited this service file.

[root@ljira1d ~]# cat /usr/lib/systemd/system/jira.service
[Unit]
Description=Atlassian Systemd Jira Service
After=syslog.target network.target

[Service]
Type=forking
Environment="JAVA_HOME=/usr/java/latest"
PIDFile=/var/atlassian/atlassian-jira/atlassian-jira-software-8.11.0-standalone/work/catalina.pid
User=jira
ExecStart=/var/atlassian/atlassian-jira/atlassian-jira-software-8.11.0-standalone/bin/start-jira.sh
ExecStop=/var/atlassian/atlassian-jira/atlassian-jira-software-8.11.0-standalone/bin/stop-jira.sh

[Install]
WantedBy=multi-user.target

ran: systemctl daemon-reload after change to file.