jira 6.4.6 to jira 7.0 upgrade

Mahendar D December 2, 2019

Hi team,

 

After upgrading jira 6.4.6 with jira 7.0 not able to start jira.

 

getting error like this.

 

2019-12-02 16:45:53,360 localhost-startStop-1 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.pyxis.greenhopper.jira]
2019-12-02 16:45:53,380 localhost-startStop-1 INFO [c.a.j.p.e.bamboo.service.PlanStatusUpdateServiceImpl] Job 'com.atlassian.jira.plugin.ext.bamboo.service.PlanStatusUpdateServiceImpl:job' scheduled to run every 60000ms
2019-12-02 16:45:53,902 localhost-startStop-1 INFO [c.a.jira.scheduler.JiraSchedulerLauncher] Starting the JIRA Scheduler....
2019-12-02 16:45:53,933 localhost-startStop-1 INFO [c.a.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler started.
2019-12-02 16:45:54,568 localhost-startStop-1 INFO [c.a.jira.startup.EmbeddedDatabaseMigrator] Starting legacy HSQL embedded database import: C:\Program Files\Atlassian\Application Data\JIRA\export\hsql-migration.zip
2019-12-02 16:45:54,573 localhost-startStop-1 ERROR [c.a.jira.startup.LauncherContextListener] Unable to start JIRA.
java.lang.IllegalStateException: You cannot perform an import with an invalid validation result. Errors: {}
Error Messages: [This JIRA installation has already been set up. Please perform an XML restore instead of an import during setup.]
at com.atlassian.jira.bc.dataimport.DefaultDataImportService.doImport(DefaultDataImportService.java:271)
at com.atlassian.jira.startup.EmbeddedDatabaseMigrator.importAndContinue(EmbeddedDatabaseMigrator.java:122)
at com.atlassian.jira.startup.EmbeddedDatabaseMigrator.start(EmbeddedDatabaseMigrator.java:57)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:137)
at com.atlassian.jira.startup.DefaultJiraLauncher$$Lambda$16/847617805.run(Unknown Source)
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:121)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:90)
at com.atlassian.jira.startup.DefaultJiraLauncher$$Lambda$2/1027229912.run(Unknown Source)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:88)
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:79)
... 5 filtered
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
02-Dec-2019 16:45:55.089 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8085"]
02-Dec-2019 16:45:55.108 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 184741 ms
log4j:WARN No appenders could be found for logger (com.amazonaws.jmx.spi.SdkMBeanRegistry).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
2019-12-02 16:46:16,230 Caesium-1-4 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.atlassian.plugins.base-hipchat-integration-plugin-api]
2019-12-02 16:46:17,456 Caesium-1-2 INFO ServiceRunner [c.a.j.p.h.service.connect.InstallGlancesJobHandler] Running InstallGlancesJobHandler...
2019-12-02 16:46:17,458 Caesium-1-2 INFO ServiceRunner [c.a.j.p.h.service.connect.InstallGlancesJobHandler] There is no link to HipChat, no need to install glances.
2019-12-02 16:46:18,253 Caesium-1-4 INFO [c.a.j.p.h.service.ping.RefreshConnectionStatusJobHandler] Running RefreshConnectionStatusJobHandler...
2019-12-02 16:48:04,559 Modification Check:thread-1 INFO [c.a.jira.startup.JiraStartupLogger]

___ Modifications ___________________________

Modified Files : jira-application.properties
Removed FilesScreenshot (83).png

1 answer

0 votes
Alexis Robert
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 2, 2019

Hi @Mahendar D , 

 

the error message says the instance is already setup : 

[This JIRA installation has already been set up. Please perform an XML restore instead of an import during setup.]

 

Can you try restarting Jira ? If you get access to the interface, you should then try to restore your XML backup from the Administration menu.

 

Let me know if this helps, 

 

--Alexis

Suggest an answer

Log in or Sign up to answer