JIRA crashes daily with no error.

atlassian-jira.log output:


2017-07-15 11:36:14,950 Caesium-1-2 INFO ServiceRunner [c.a.j.p.h.service.connect.InstallGlancesJobHandler] There is no link to HipChat, no need to install glances.
2017-07-15 12:36:10,964 Caesium-1-3 INFO ServiceRunner [c.a.j.p.h.service.ping.RefreshConnectionStatusJobHandler] Running RefreshConnectionStatusJobHandler...
2017-07-15 12:36:14,950 Caesium-1-3 INFO ServiceRunner [c.a.j.p.h.service.connect.InstallGlancesJobHandler] Running InstallGlancesJobHandler...
2017-07-15 12:36:14,950 Caesium-1-3 INFO ServiceRunner [c.a.j.p.h.service.connect.InstallGlancesJobHandler] There is no link to HipChat, no need to install glances.
2017-07-15 14:30:25,584 localhost-startStop-1 INFO [c.a.jira.startup.JiraHomeStartupCheck] The jira.home directory '/var/atlassian/application-data/jira' is validated and locked for exclusive use by this instance.
2017-07-15 14:30:25,697 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger]

****************
JIRA starting...
****************

-----------------------------------

The java process was gone in 2017-07-15 12:36:14, and then I manuly start JIRA by ./start-jira.sh in 2017-07-15 14:30:25.

2 answers

0 vote

Can you show us the ends of the <jira home>/log/atlassian-jira.log and <jira install>/logs/catalina.out at the time of one of your crashes please?

These two will almost always contain an error message telling us why it halted. 

2018-03-22 11:20:21,752 http-nio-8080-exec-11 WARN gitlab 680x850261x1 7unhu2 10.12.253.32,10.64.255.67 /rest/api/2/issue/96579/remotelink [c.a.j.structure.event.StructureIssueListener] Failed to get remote issue links for global ID null
2018-03-22 11:21:45,652 Caesium-1-3 INFO ServiceRunner [c.a.j.p.h.service.ping.RefreshConnectionStatusJobHandler] Running RefreshConnectionStatusJobHandler...
2018-03-22 11:21:45,853 Caesium-1-2 INFO ServiceRunner [c.a.j.p.h.service.connect.InstallGlancesJobHandler] Running InstallGlancesJobHandler...
2018-03-22 11:21:45,856 Caesium-1-2 INFO ServiceRunner [c.a.j.p.h.service.connect.InstallGlancesJobHandler] The plugin is not configured, no need to install glances.

Jira was not accessible after this for few minutes but jira service was running fine. After some time it automatically accessible. we do know it is behaving like this.  

That's not a crash report, just a warning about a broken link.

If that genuinely is the last thing in the log before Jira halts, then it's not a problem with Jira.

It could still be Tomcat that is failing - what is in the log at the time of a crash for Tomcat?  (Catalina.out)

We are also facing same issue. JIRA become in accessible for 10-15 mins and then come back.

Jira service is running in that time. 

Was there are solution to this?

 

Please advice.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Sarah Schuster
Posted Mar 28, 2018 in Jira Software

Can a company’s culture make or break agile adoption?

Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...

12,060 views 15 13
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you