nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Manual upgrade of Jira Server leads to Setup Wizard

AMI IT

Hi everyone,

I performed a manual upgrade of Jira Server based on Atlassian documentation and Atlassian support instruction. When I run Jira post-upgrade, I get the setup wizard (SetupMode!default.jspa) instead of the upgrade success page. I need to either get to the upgrade success page or revert back and run my old instance of Jira as it was, but whether I run the new or old version of Jira (via ./start-jira.sh), the result is the same: the setup wizard.

Any help would be appreciated.

Accepted answers

All comments

PD Sheehan

It would seem that perhaps Jira is not finding your jira-home directory.

How were you specifying that before? Using the JIRA_HOME environment variable?

If unsure, you can try to set it in the <jira_install_dir>/atlassian-jira/WEB-INF/classes/jira-application.properties

AMI IT

Hi Peter, and thank you. I have JIRA_HOME set in several places (all to the same path), including in jira-application.properties. I have checked directory permissions, dbconfig.xml file existence and permissions, etc. - but Jira just keeps showing me the setup screen when I stop and start it. I tried this, too: https://community.atlassian.com/t5/Jira-Software-questions/How-do-I-use-my-renewed-license-with-the-existing-server/qaq-p/1417671

Any other ideas?

PD Sheehan

Review catalina.out, you might get some clues.

Also look for hidden files in jira-home. If you see an empty file called .jira-home.lock (and with a created date that matches your start time) that means that jira found the jira-home and is using it. Then you can further review the <jira-home>/log/atlassian-jira.log

If the file is not there, the startup didn't identify the jira-home directory or didn't have access to it.

AMI IT

The lock file is indeed present, so that rules out a pathing issue. The log shows that the dbconfig.xml file is being read, but then there's a message that "The database is not yet configured". I know the db is configured because we've been using it for a long time, and I've inspected the dbconfig.xml file and everything looks correct.

Here's the tail of the atlassian-jira.log file that shows the db issue:

2021-04-24 18:20:01,454-0600 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /srv/jira/jira-data/dbconfig.xml
2021-04-24 18:20:01,475-0600 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]
2021-04-24 18:20:01,556-0600 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running Jira startup checks.
2021-04-24 18:20:01,557-0600 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Jira pre-database startup checks completed successfully.
2021-04-24 18:20:01,613-0600 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Database Checklist Launcher on post-database-configured-but-pre-database-activated queue
2021-04-24 18:20:01,614-0600 JIRA-Bootstrap INFO [c.a.j.config.database.DatabaseConfigurationManagerImpl] The database is not yet configured. Enqueuing Post database-configuration launchers on post-database-activated queue
2021-04-24 18:20:01,621-0600 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

atl-gruland