Atlassian Jira not starting, shows setup page in browser and database is not yet configured in logs

Written by Claudio Kuenzler - 0 comments

Published on September 8th 2020 - Listed in Atlassian Database MySQL

---

After a Jira's database was copied from a production to a test environment (to create an up to date test environment), Jira wouldn't start anymore. Instead the logs showed the following informational events:

2020-09-08 07:55:49,543 JIRA-Bootstrap INFO      [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup ended
2020-09-08 07:55:49,554 JIRA-Bootstrap INFO      [c.a.jira.i18n.CachingI18nFactory] [i18n-caching-factory] Starting
2020-09-08 07:55:49,699 JIRA-Bootstrap INFO      [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from /var/atlassian/application-data/jira/dbconfig.xml
2020-09-08 07:55:49,712 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]
2020-09-08 07:55:49,769 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2020-09-08 07:55:49,769 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger] JIRA pre-database startup checks completed successfully.
2020-09-08 07:55:49,836 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
2020-09-08 07:55:49,836 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
2020-09-08 07:55:49,861 JIRA-Bootstrap INFO      [c.a.jira.startup.LauncherContextListener] Memory Usage:
    ---------------------------------------------------------------------------------
      Heap memory     :  Used:  777 MiB.  Committed: 1591 MiB.  Max: 4066 MiB
      Non-heap memory :  Used:   72 MiB.  Committed:   88 MiB.  Max: 1536 MiB
    ---------------------------------------------------------------------------------
      TOTAL           :  Used:  849 MiB.  Committed: 1679 MiB.  Max: 5602 MiB
    ---------------------------------------------------------------------------------

Important hint here: The database is not yet configured. This makes no sense obviously as the database is coming right from a Jira running in production.

When browsing to the URL of this test instance, the Jira setup page would be shown:

Check file permissions

Obviously there had been a couple of migrations happening to create an up to date test environment:

• Sync of /var/atlassian/application-data/jira from PROD to TEST
• Dump database in PROD, transfer and import on TEST
• Adjusting /var/atlassian/application-data/jira/dbconfig.xml for the new test database
  
• Adjust a few Tomcat parameters to create a proper test environment (see Creating a test environment for Jira)

Obviously a very small problem with a big impact. But luckily with an even quicker fix.

Add a comment

Show form to leave a comment

Comments (newest first)

No comments yet.