Jira Service Stopped on Server

[Krishna Kumar Yadav]

Hi All,

Jira is running as a service on Redhat server version 7.6 . All of sudden, Jira service was not running on the server. As per logs, no heap memory build up, no space issue, no threads being idle for long time. 

I have checked (/var/log/messages) log for any related errors, like oomkiller actions, but there is nothing that could have stopped the service.

Please help to troubleshoot this issue further.

Regards,

Krishna

[Nic Brough -Adaptavist-]

First, look at the application log (jira home/log/atlassian-jira.log) - what does the last chunk of it say?  It sounds like you've looked for some errors, but if the application was stopped correctly, it should show shutdown messages, and if it failed, there will be an indication of why.

Second, check the service log to see why the application server stopped (jira install/log/catalina.out)

If neither of those has any shutdown messaging, then you'll need to ask the humans or the server why they issued a hard "kill process" that shut it down without any logging.

[Krishna Kumar Yadav]

Thank you for the suggestions.

There are no messages of application being stopped. It was like someone had killed the service but my team does not rights to kill any process.

I have check with unix admin and it was not killed from their end. 

[Nic Brough -Adaptavist-]

If neither log shows any logging of an error or a shut-down message, then either the log was unwritable at the time of an error, or something or someone killed the process.  There is no other way to get into this position.

[Milan Chheda [INFOSYSTA]]

Check logs from installation as well as home directory. I believe, they would be at:

/opt/atlassian/jira/logs

/var/atlassian/application-data/logs/atlassian-jira.log

Above logs would help you as well us to better understand as to why JIRA Service stopped working.

[Krishna Kumar Yadav]

Thank you for the suggestion. but there were no messages regarding service stop 

[Milan Chheda [INFOSYSTA]]

That's kinda not possible unless the logs are not writable. Probably try to start the service again and check for those logs. There definitely has to be logs initially in installation directory followed by home directory if the application boots up.