Error during upgrade form 6.3.15 to 7.2

Marcin Beczynski October 26, 2016

Hey,

I getting error performing upgrade from 6.3.15 to 7.2 log describe bellow. I arlady try remove index cache and remove plugin cache also disable plugin what could make problem ( leave only script runner ) also try this instrucion and still geting error info

 

Thanks ind advice for all help and ints

 

2016-10-27 06:59:18,674 Thread-45 ERROR      [c.m.secureFields.commons.JiraCompatibilityServiceImpl] secure-fields.plugin-compatibility.error.plugin-incompatible.message.
2016-10-27 06:59:19,414 JIRA-Bootstrap INFO      [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1): [com.pyxis.greenhopper.jira], 45 seconds remaining
2016-10-27 06:59:20,415 JIRA-Bootstrap INFO      [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (1): [com.pyxis.greenhopper.jira], 44 seconds remaining
2016-10-27 06:59:24,114 JIRA-Bootstrap INFO      [c.a.j.plugins.monitor.MonitoringScheduler] Scheduling metrics collector to run every 10000ms...
2016-10-27 06:59:24,123 JIRA-Bootstrap INFO      [c.a.j.p.monitor.rrd4j.RrdUpdater] Reusing existing RrdDb: /var/atlassian/application-data/jira/monitor/ConnectionPoolGraph.rrd4j
2016-10-27 06:59:24,142 JIRA-Bootstrap INFO      [c.a.j.p.monitor.rrd4j.RrdUpdater] Reusing existing RrdDb: /var/atlassian/application-data/jira/monitor/DatabaseReadWritesGraph.rrd4j
2016-10-27 06:59:24,153 JIRA-Bootstrap INFO      [c.a.j.plugins.monitor.MonitorLauncher] Started JIRA monitoring
2016-10-27 06:59:26,202 JIRA-Bootstrap INFO      [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup ended
2016-10-27 06:59:27,071 JIRA-Bootstrap ERROR      [c.a.jira.service.OfBizServiceConfigStore] Unable to create a service config for service with the name : Subversion Index Update Service
2016-10-27 06:59:27,074 JIRA-Bootstrap ERROR      [c.a.jira.service.OfBizServiceConfigStore] The class 'com.atlassian.jira.plugin.ext.subversion.revisions.scheduling.clustersafe.UpdateSvnIndexService' could not be found.  This can happen when a plugin is uninstalled or disabled
2016-10-27 06:59:27,074 JIRA-Bootstrap ERROR      [c.a.jira.service.OfBizServiceConfigStore] A NoOp Service has been returned and hence 'Subversion Index Update Service' will not do anything until fixed.
2016-10-27 06:59:27,116 JIRA-Bootstrap ERROR      [c.a.jira.service.OfBizServiceConfigStore] Unable to create a service config for service with the name : Subversion Index Update Service
2016-10-27 06:59:27,118 JIRA-Bootstrap ERROR      [c.a.jira.service.OfBizServiceConfigStore] The class 'com.atlassian.jira.plugin.ext.subversion.revisions.scheduling.clustersafe.UpdateSvnIndexService' could not be found.  This can happen when a plugin is uninstalled or disabled
2016-10-27 06:59:27,118 JIRA-Bootstrap ERROR      [c.a.jira.service.OfBizServiceConfigStore] A NoOp Service has been returned and hence 'Subversion Index Update Service' will not do anything until fixed.
2016-10-27 06:59:27,159 JIRA-Bootstrap ERROR      [c.a.jira.service.OfBizServiceConfigStore] Unable to create a service config for service with the name : Subversion Index Update Service
2016-10-27 06:59:27,161 JIRA-Bootstrap ERROR      [c.a.jira.service.OfBizServiceConfigStore] The class 'com.atlassian.jira.plugin.ext.subversion.revisions.scheduling.clustersafe.UpdateSvnIndexService' could not be found.  This can happen when a plugin is uninstalled or disabled
2016-10-27 06:59:27,161 JIRA-Bootstrap ERROR      [c.a.jira.service.OfBizServiceConfigStore] A NoOp Service has been returned and hence 'Subversion Index Update Service' will not do anything until fixed.
2016-10-27 06:59:27,324 JIRA-Bootstrap INFO      [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml
2016-10-27 06:59:27,343 JIRA-Bootstrap INFO      [c.a.j.instrumentation.external.DatabaseExternalGauges] Installing DBCP monitoring instruments: DatabaseExternalGauges.JiraDbcpInstruments[instruments=[DBCP_MAX, DBCP_ACTIVE, DBCP_IDLE],objectName=com.atlassian.jira:name=BasicDataSource]
2016-10-27 06:59:27,488 JIRA-Bootstrap INFO      [c.a.jira.tenancy.DefaultTenantManager] Instance has a tenant. Now running [Tenanted launchers]
2016-10-27 06:59:27,489 JIRA-Bootstrap INFO      [c.a.jira.startup.DefaultInstantUpgradeManager] Now running [Late startup launchers]
2016-10-27 06:59:27,490 JIRA-Bootstrap INFO      [c.a.jira.upgrade.ConsistencyCheckImpl] Checking JIRA consistency
2016-10-27 06:59:27,508 JIRA-Bootstrap INFO      [c.a.jira.upgrade.ConsistencyCheckImpl] The Server ID for this JIRA instance is: [A5PX-OJIC-J4WZ-MOEX]
2016-10-27 06:59:28,261 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger]
2016-10-27 06:59:28,292 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger]
2016-10-27 06:59:28,350 JIRA-Bootstrap INFO      [c.a.plugin.manager.DefaultPluginManager] Plugin system lateStartup begun
2016-10-27 06:59:29,928 JIRA-Bootstrap INFO      [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (5): [com.tempoplugin.tempo-plan-core, com.tempoplugin.tempo-accounts, com.tempoplugin.tempo-teams, is.origo.jira.tempo-plugin, com.tempoplugin.tempo-core], 60 seconds remaining
2016-10-27 06:59:30,929 JIRA-Bootstrap INFO      [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (2): [com.tempoplugin.tempo-plan-core, is.origo.jira.tempo-plugin], 58 seconds remaining
2016-10-27 06:59:31,930 JIRA-Bootstrap INFO      [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (2): [com.tempoplugin.tempo-plan-core, is.origo.jira.tempo-plugin], 57 seconds remaining
2016-10-27 06:59:31,960 Modification Check:thread-1 INFO      [c.a.jira.startup.JiraStartupLogger]
2016-10-27 06:59:32,932 JIRA-Bootstrap INFO      [c.a.plugin.util.WaitUntil] Plugins that have yet to be enabled: (2): [com.tempoplugin.tempo-plan-core, is.origo.jira.tempo-plugin], 56 seconds remaining
2016-10-27 06:59:35,782 JIRA-Bootstrap INFO      [c.a.plugin.manager.DefaultPluginManager] Plugin system lateStartup ended
2016-10-27 06:59:35,821 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger]
2016-10-27 06:59:36,117 JIRA-Bootstrap INFO      [c.a.jira.upgrade.UpgradeManagerImpl] Detected that an upgrade is needed; existing data at build 6346
2016-10-27 06:59:36,117 JIRA-Bootstrap INFO      [c.a.jira.upgrade.UpgradeManagerImpl] Exporting the existing data..
2016-10-27 07:04:05,737 JIRA-Bootstrap INFO      [c.a.j.bc.dataimport.DefaultExportService] Data export completed in 269348ms. Wrote 15466041 entities to export in memory.
2016-10-27 07:04:05,739 JIRA-Bootstrap INFO      [c.a.j.bc.dataimport.DefaultExportService] Attempting to save the Active Objects Backup
2016-10-27 07:04:22,246 JIRA-Bootstrap INFO      [c.a.j.bc.dataimport.DefaultExportService] Finished saving the Active Objects Backup
2016-10-27 07:04:22,272 JIRA-Bootstrap INFO      [c.a.jira.upgrade.UpgradeManagerImpl] Exported pre-upgrade data to: /var/atlassian/application-data/jira/export/jira_autoexport_20161027_065936.zip
2016-10-27 07:04:22,272 JIRA-Bootstrap INFO      [c.a.jira.upgrade.UpgradeManagerImpl] ___ Performing Upgrade ____________________
2016-10-27 07:04:22,543 JIRA-Bootstrap INFO      [c.a.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: JRA-34394: Fixing incorrect watch count for cloned issues
2016-10-27 07:04:24,670 JIRA-Bootstrap ERROR      [c.a.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: Indexing completed with 1 errors
2016-10-27 07:04:45,203 JIRA-Bootstrap ERROR      [c.a.s.core.lifecycle.DefaultLifecycleManager] LifecycleAware.onStart() failed for component with class 'com.atlassian.greenhopper.Launcher' from plugin 'com.pyxis.greenhopper.jira'
2016-10-27 07:04:50,283 JIRA-Bootstrap ERROR      [c.a.s.core.lifecycle.DefaultLifecycleManager] LifecycleAware.onStart() failed for component with class 'com.onresolve.scriptrunner.runner.JqlFunctionsManagerImpl' from plugin 'com.onresolve.jira.groovy.groovyrunner'
2016-10-27 07:04:50,303 JIRA-Bootstrap INFO      [c.a.j.p.e.bamboo.service.PlanStatusUpdateServiceImpl] PlanStatusUpdateJob scheduled to run every 60 seconds
2016-10-27 07:04:50,970 JIRA-Bootstrap INFO      [c.a.j.c.embedded.ofbiz.IndexedUserDao] Reindex all users took: 492.2 ms
2016-10-27 07:04:50,971 JIRA-Bootstrap INFO      [c.a.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: Johnson events detected.
2016-10-27 07:04:50,981 JIRA-Bootstrap INFO      [c.a.jira.startup.DefaultInstantUpgradeManager] Late startup launchers took 323s
2016-10-27 07:04:50,986 JIRA-Bootstrap INFO      [c.a.jira.startup.LauncherContextListener] Memory Usage:

 

 

An error occurred performing JIRA upgrade

The data before the upgrade has been exported to /var/atlassian/application-data/jira/export/jira_autoexport_20161027_065936.zip
2016-10-27 07:04:24
error
Exception thrown during upgrade: Indexing completed with 1 errors
com.atlassian.jira.index.IndexingFailureException: Indexing completed with 1 errors
	at com.atlassian.jira.index.AccumulatingResultBuilder$CompositeResult.await(AccumulatingResultBuilder.java:187)
	at com.atlassian.jira.issue.index.DefaultIndexManager.obtain(DefaultIndexManager.java:785)
	at com.atlassian.jira.issue.index.DefaultIndexManager.await(DefaultIndexManager.java:761)
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:541)
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:517)
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:500)
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndexIssues(DefaultIndexManager.java:391)
	at com.atlassian.jira.issue.index.DefaultIndexManager.reIndex(DefaultIndexManager.java:466)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.atlassian.jira.config.component.SwitchingInvocationHandler.invoke(SwitchingInvocationHandler.java:22)
	at com.sun.proxy.$Proxy13.reIndex(Unknown Source)
	at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build64001.fixBrokenIssues(UpgradeTask_Build64001.java:155)
	at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build64001.doUpgrade(UpgradeTask_Build64001.java:71)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSuccess(UpgradeManagerImpl.java:708)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.runUpgradeTasks(UpgradeManagerImpl.java:599)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgrade(UpgradeManagerImpl.java:483)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:425)
	at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:369)
	at com.atlassian.jira.upgrade.UpgradeLauncher.checkIfUpgradeNeeded(UpgradeLauncher.java:90)
	at com.atlassian.jira.upgrade.UpgradeLauncher.start(UpgradeLauncher.java:47)
	at com.atlassian.jira.startup.ActiveServicesLauncher.start(ActiveServicesLauncher.java:49)
	at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postTenantArrived$4(DefaultJiraLauncher.java:178)
	at com.atlassian.jira.startup.DefaultInstantUpgradeManager$StartupTask.run(DefaultInstantUpgradeManager.java:139)
	at com.atlassian.jira.startup.DefaultInstantUpgradeManager.runTask(DefaultInstantUpgradeManager.java:55)
	at com.atlassian.jira.startup.DefaultInstantUpgradeManager.doNowOrWhenInstanceBecomesActive(DefaultInstantUpgradeManager.java:42)
	at com.atlassian.jira.startup.DefaultJiraLauncher.postTenantArrived(DefaultJiraLauncher.java:171)
	at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDBActivated$3(DefaultJiraLauncher.java:159)
	at com.atlassian.jira.tenancy.DefaultTenantManager.doNowOrWhenTenantArrives(DefaultTenantManager.java:55)
	at com.atlassian.jira.startup.DefaultJiraLauncher.postDBActivated(DefaultJiraLauncher.java:156)
	at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:145)
	at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:298)
	at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:194)
	at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:135)
	at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:101)
	at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
	at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:99)
	at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:149)
	at java.lang.Thread.run(Thread.java:745)

1 answer

1 accepted

1 vote
Answer accepted
Jonas Andersson
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 Leaders.
October 26, 2016

I upgraded from 6.2.1 to 7.1.9 and i HAD to step-stone it like this:

6.2.1 -> 6.3.15

6.3.15 -> 6.4.13

6.4.13 -> 7.1.9

You can obviously skip the first upgrade, but i am pretty sure you have to pass 6.4.13 before going to a 7.x install, have a feeling you can go all the way from 6.4.13 to 7.2.x

 

Some other takeaways:

  • Don't reindex between the upgrades, wait until you made the last upgrade as this just creates indexes for the UI, ignore that you don't see assigned issues (or issues in general)
  • After each upgrade, upgrade all plugins starting with UPM, if anything is incompatible, just disable them till you see a updated version and re-enabled them then.
  • Save you dbconfig.xml, cacerts, server.xml, setenv.sh, web.xml and other files that might have been modifed. On each upgrade you will see a bunch of files that are modified. Created folders named after the current version and copy them all there. This allows for a fast fixes once you reached the destination version.
  • After all upgrades are done, restore SSL settings, cacerts files. Don't just restore server.xml, but look at both the new files and your original and implement the diffrences.
  • Rebuild your indexes.

Suggest an answer

Log in or Sign up to answer