The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade from 8.10.1 to 8.11 crashes JIRA

Cognizant Mobility
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 28, 2020

JIRA Service is unavailable an run to timeout

 

image.png

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 28, 2020

That tells us that the service is not responding when the proxy asks it for something.

This usually means it is not running (usually you'll get that message immediately), or that it is doing something and cannot serve (you'll get this message after waiting for a short time).

If the system is upgrading, it may not have reached a point where it can serve anything up, so you'll see the timeout there.  You'll need to leave it to finish (one of my current projects has a 4 hour upgrade process - you start Jira, and it makes structural changes to the database which take hours, so for a large Jira you may need quite a wait).

If it's not in the process of upgrading, then you should read the application logs to find out why it is not serving or why it has shut down.

DEPLOYMENT TYPE
SERVER
VERSION
8.10.1
TAGS
AUG Leaders

Atlassian Community Events