root@vmi466451:~# sudo service jira start
root@vmi466451:~# systemctl status jira.service
● jira.service - Atlassian Jira
Loaded: loaded (/lib/systemd/system/jira.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2020-11-25 08:48:04 CET; 113ms ago
Process: 53209 ExecStart=/opt/atlassian/jira/bin/start-jira.sh (code=exited, status=0/SUCCESS)
Process: 53304 ExecStop=/opt/atlassian/jira/bin/stop-jira.sh (code=exited, status=1/FAILURE)
Main PID: 53255 (code=exited, status=0/SUCCESS)
Nov 25 08:48:04 vmi466451.contaboserver.net stop-jira.sh[53316]: `UOJ
Nov 25 08:48:04 vmi466451.contaboserver.net stop-jira.sh[53316]:
Nov 25 08:48:04 vmi466451.contaboserver.net stop-jira.sh[53316]: Atlassian Jira
Nov 25 08:48:04 vmi466451.contaboserver.net stop-jira.sh[53316]: Version : 8.13.1
Nov 25 08:48:04 vmi466451.contaboserver.net stop-jira.sh[53316]:
Nov 25 08:48:04 vmi466451.contaboserver.net stop-jira.sh[53304]: If you encounter issues starting or stopping Jira, please see the Troubleshooting guide at https://docs.atlassian.com/jira/jadm-docs>
Nov 25 08:48:04 vmi466451.contaboserver.net stop-jira.sh[53304]: Server startup logs are located in /opt/atlassian/jira/logs/catalina.out
Nov 25 08:48:04 vmi466451.contaboserver.net stop-jira.sh[53304]: PID file found but either no matching process was found or the current user does not have permission to stop the process. Stop abort>
Nov 25 08:48:04 vmi466451.contaboserver.net systemd[1]: jira.service: Control process exited, code=exited, status=1/FAILURE
Nov 25 08:48:04 vmi466451.contaboserver.net systemd[1]: jira.service: Failed with result 'exit-code'.
