Upgrade from 7.13 to 8.5.9 failing (LINUX - CentOS 7.8)

Jasper Connery

Hello,

 

I am attempting to upgrade our test instance of JIRA (standalone) from 7.13 to 8.5.9 and the upgrade is failing with:

 

2020-10-16 10:56:25,470+1300 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. JIRA will be locked.

 

To upgrade the server I copied over the setenv.sh and server.xml files from the Jira Home directory into the extracted upgrade directory, then navigated to the /bin folder and ran: ./start-jira.sh as per these instructions:

 

https://confluence.atlassian.com/jiracore/upgrading-jira-server-976161476.html 

 

I have disabled the antivirus (clamav used to scan files).

 

I increased the RAM arguments for java.

 

Is there somewhere that these startup checks are ticked off? Somewhere i can see which one failed?

 

The last few lines of catalina.out are:

 

16-Oct-2020 10:56:25.208 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["https-jsse-nio-8443"]
16-Oct-2020 10:56:25.357 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
16-Oct-2020 10:56:25.383 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8081"]
16-Oct-2020 10:56:25.389 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 4771 ms
2020-10-16 10:56:25,469+1300 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2020-10-16 10:56:25,470+1300 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. JIRA will be locked.
2020-10-16 10:56:25,525+1300 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 273 MiB. Committed: 1153 MiB. Max: 2026 MiB
Non-heap memory : Used: 42 MiB. Committed: 64 MiB. Max: 1536 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 315 MiB. Committed: 1217 MiB. Max: 3562 MiB
---------------------------------------------------------------------------------

 

Cheers

Daniel Ebers

Hi Jasper,

welcome to the Atlassian Community!

Looking at the logs is the best advise you can get. The problem right now is that the snippet you showed is not showing the root cause.
The error you are receiving "Jira will be locked" is a result from something else, not a symptom.

There must be something else in the logs - in case you can post it here somebody is more likely to tell what's going on.
Right now it must be assumed something went wrong but it could have thousands of reasons - I am afraid.

Cheers,
Daniel