Database ConfigurationManager not available

Andrey Permyakov January 26, 2020

Yesterday, the virtual servers rebooted, for this server they turned off and began the migration. After turning on I get an error in the logs:

2020-01-26 17:19:37,188 localhost-startStop-1 WARN [o.a.catalina.util.SessionIdGeneratorBase] Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [9,452] milliseconds.
2020-01-26 17:19:38,149 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] Could not execute health check, DatabaseConfigurationManager not available.
2020-01-26 17:19:38,150 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] Could not execute health check, DatabaseConfigurationManager not available.
2020-01-26 17:19:38,150 JIRA-Bootstrap ERROR [c.a.jira.startup.DefaultJiraLauncher] JIRA has failed to start because of the following errors: [(Event: Level = (EventLevel: fatal) , Key = (EventType: startup-unexpected) , Desc = We couldn't start JIRA , Exception = An error occurred while trying to start JIRA. We can't give you any more detail right now, we suggest checking the logs for more detail and contacting our support team.<br/>See our documentation for more information on contacting our support team and creating a support zip.), (Event: Level = (EventLevel: fatal) , Key = (EventType: database) , Desc = Could not execute health check, DatabaseConfigurationManager not available. , Exception = ]

tried to restart with dbconfig removal Tried connecting to a new clean base Nothing helps.

Jira 7.12.3

Jira server centos 7

db mssql 14

1 answer

1 accepted

0 votes
Answer accepted
Andrey Permyakov January 27, 2020

This post helped

Suggest an answer

Log in or Sign up to answer