The host you point to might be running - ping was successful - but there is no database running, or. If this is not the case two things may be happening: Nmap done: 1 IP address (1 host up) scanned in 13.27 secondsįix: Check your database and database settings for external connections Not shown: 498 closed ports, 498 filtered ports Ping your database serverĬan you ping your Database server? Take the URL for your database that's in your dbconfig.xml and ping your database Network issueĬheck to see if your network is up and check if your database is reachable for your JIRA instance. If you have issues with the embedded H2 database, you can refer to the following article to verify access to it: Access the H2 embedded database. These steps do not apply when using the embedded H2 database. Given that there's a number of reasons this could be happening, there are a few things you may need to check to resolve this. Without a database, it can't read any previously created Issues or store newly created issues. 
The JIRA instance needs a database in order to run. Network connection not available/offline.General network issues that prevent JIRA from connecting to your database include:.The database specified is not the JIRA database.Your database user doesn't have the correct permissions to connect to the database.Username/Password for your database are incorrect.
The configuration in your dbconfig.xml is incorrect.The Database Connection check verifies that JIRA can connect to a Database, as this is vital for JIRA to run.
Jira client connection login failed upgrade#
ĭuring Installation, Upgrade or Startup, JIRA performs a number of checks. This article only applies to Atlassian products on the server and data center platforms. Platform notice: Server and Data Center only.
0 kommentar(er)
