Upgrading Jira from 4.4.5 to 6.4

[Fr0zt]

Hello.

I am trying to perform an upgrade from Jira 4.4.1 to Jira 7.10.

I am using MySQL 5.5, which is compactible with all of this jira versions.

My database, to jira 4.4.1 was built by doing the following query:

create database jiradb character set utf8; (as I read in Jira documentation).

I read in the documentation the upgrade should be done following this path:

Jira 4.4.1 -> Jira 4.4.5 -> Jira 6.4 -> Jira 7.0 -> jira 7.10.

https://confluence.atlassian.com/adminjiraserver0710/upgrading-jira-applications-using-the-installer-953144306.html

I've done the upgrade to Jira 4.4.5 and I think it went ok.

Now, doing the upgrade to Jira 6.4 I am having issues and Jira will not startup. Instead I get this message in my browser:

" Error occurred while starting component 'com.atlassian.jira.service.DefaultServiceManager'. caused by: Error creating underlying Quartz scheduler".

When I examined the logs I found this:

" 

2018-09-13 09:24:26,499 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger]

********************************************************************************
JIRA 6.4 build: 64014 started. You can now access JIRA through your web browser.
********************************************************************************

2018-09-13 09:24:26,577 localhost-startStop-1 ERROR [atlassian.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked.
2018-09-13 09:24:26,577 localhost-startStop-1 INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: JIRA startup checklist failed.
2018-09-13 09:24:26,827 localhost-startStop-1 WARN [jira.plugin.customfield.CustomFieldSearcherModuleDescriptorsImpl] Custom field searcher module: com.atlassian.jira.plugin.system.customfieldtypes:checkboxsearcher is invalid. Null being returned.
2018-09-13 09:24:26,890 localhost-startStop-1 WARN [jira.plugin.customfield.CustomFieldSearcherModuleDescriptorsImpl] Custom field searcher module: com.atlassian.jira.plugin.system.customfieldtypes:checkboxsearcher is invalid. Null being returned.
2018-09-13 09:24:27,140 localhost-startStop-1 INFO [jira.index.ha.DefaultIndexRecoveryManager] Latest index date: {77875002-02-10 06:43:21}, Latest DB date: {2018-09-12 17:36:54}
2018-09-13 09:24:27,140 localhost-startStop-1 INFO [atlassian.jira.startup.IndexRecoveryLauncher] Issue index is out of date with the database by more than 24 hours. Automatic recovery is not attempted
2018-09-13 09:24:27,155 localhost-startStop-1 INFO [atlassian.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 233 MiB. Committed: 474 MiB. Max: 736 MiB
Non-heap memory : Used: 180 MiB. Committed: 196 MiB. Max: 1264 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 413 MiB. Committed: 669 MiB. Max: 2000 MiB
---------------------------------------------------------------------------------
2018-09-13 09:24:27,312 localhost-startStop-1 ERROR [jira.web.dispatcher.JiraWebworkActionDispatcher]

******************************************
JIRA startup failed, JIRA has been locked.
******************************************

2018-09-13 09:24:32,405 Modification Check:thread-1 INFO [atlassian.jira.startup.JiraStartupLogger]

___ Modifications ___________________________

Modified Files : jira-application.properties
Removed Files : None

 "

How can I fix this? Can anyone help me please?

[Pedro Felgueiras · Accepted solution]

Hi @Fr0zt

Have you tried to increase the timeout of the plugin load?  

https://confluence.atlassian.com/jirakb/jira-applications-system-plugin-timeout-while-waiting-for-add-ons-to-enable-212173447.html

Reading you message it's the only thing I can remember. 

Best regards, 

Pedro Felgueiras 

[Fr0zt]

Olá :)

I've tried that now.

Jira should be up and running but I am waiting for 12 minutes and still in my browser I am waiting for the page to load...

In my logs I get this:

" 2018-09-13 10:57:49,144 localhost-startStop-1 INFO [atlassian.jira.startup.JiraHomeStartupCheck] The jira.home directory 'C:\Atlassian\Application Data\JIRA' is validated and locked for exclusive use by this instance.
2018-09-13 10:57:49,157 localhost-startStop-1 INFO [jira.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\Atlassian\Application Data\JIRA\dbconfig.xml
2018-09-13 10:57:49,306 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2018-09-13 10:57:49,306 localhost-startStop-1 INFO [atlassian.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.
2018-09-13 10:57:50,179 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Product Name is MySQL
2018-09-13 10:57:50,180 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Product Version is 5.0.15-nt
2018-09-13 10:57:50,180 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Driver Name is MySQL-AB JDBC Driver
2018-09-13 10:57:50,180 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Driver Version is mysql-connector-java-5.1.10 ( Revision: ${svn.Revision} )"

Any other ideas?

[Fr0zt]

 think I made some mistake and installed MySQL 5.0 instead of 5.5 :(

[Charlie Misonne]

Hi @Fr0zt

Does that mean increasing the plugin timeout solved a part of your problem?

I remember it can take quite some time after the "Driver Version is..." log entry.

I had an instance where this took 20min.  After that I got:

JIRA database startup checks completed successfully.

 See this Community Question as well.

You could disable auto export and see if it goes faster.

[Fr0zt]

I  upgraded my MySQL to 5.5 and it worked ok.

It was about the MySQL Version.