I have JIRA 7.5.2 installed on a CentOS 7.4 server and I noticed that there are four duplicates of the JIRA Systemd service:
[root@server ~]# systemctl list-units | grep jira
jira.service loaded active exited (null)
● jira1.service loaded failed failed (null)
jira2.service loaded active exited (null)
jira3.service loaded active running (null)
jira4.service loaded active exited (null)
Some are active, others not:
[root@server ~]# for svc in jira jira1 jira2 jira3 jira4; do systemctl status $svc; done
● jira.service - (null)
Loaded: loaded (/etc/rc.d/init.d/jira; bad; vendor preset: disabled)
Active: active (exited) since Tue 2018-10-02 08:35:37 CEST; 4h 59min ago
Docs: man:systemd-sysv-generator(8)
Process: 1155 ExecStart=/etc/rc.d/init.d/jira start (code=exited, status=0/SUCCESS)
● jira1.service - (null)
Loaded: loaded (/etc/rc.d/init.d/jira1; bad; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2018-10-02 08:35:36 CEST; 4h 59min ago
Docs: man:systemd-sysv-generator(8)
Process: 1162 ExecStart=/etc/rc.d/init.d/jira1 start (code=exited, status=127)
● jira2.service - (null)
Loaded: loaded (/etc/rc.d/init.d/jira2; bad; vendor preset: disabled)
Active: active (exited) since Tue 2018-10-02 08:35:37 CEST; 4h 59min ago
Docs: man:systemd-sysv-generator(8)
Process: 1157 ExecStart=/etc/rc.d/init.d/jira2 start (code=exited, status=0/SUCCESS)
● jira3.service - (null)
Loaded: loaded (/etc/rc.d/init.d/jira3; bad; vendor preset: disabled)
Active: active (running) since Tue 2018-10-02 08:35:37 CEST; 4h 59min ago
Docs: man:systemd-sysv-generator(8)
Process: 1158 ExecStart=/etc/rc.d/init.d/jira3 start (code=exited, status=0/SUCCESS)
● jira4.service - (null)
Loaded: loaded (/etc/rc.d/init.d/jira4; bad; vendor preset: disabled)
Active: active (exited) since Tue 2018-10-02 08:35:37 CEST; 4h 59min ago
Docs: man:systemd-sysv-generator(8)
Process: 1159 ExecStart=/etc/rc.d/init.d/jira4 start (code=exited, status=0/SUCCESS)
They're all disabled at boot.
Another JIRA server I have lists two duplicate services.
Why is that? This might be related to this issue, although there is only one Java process running for JIRA and is owned by the "jira" user, as it should.