bug post upgrade

Question

Hello

We are upgrading a production environmentbut after the upgrade we can not access to the data we have this error message you can see it in the screenshot

"Database: JIRA couldn't connect to your database"

We have checked the database is up and running.

Could you help us, how we can resolve this issue ?

Regards

Nic Brough -Adaptavist- · Answer

Yes.  The log says:

This could be because:
        - Your database isn't running
        - The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
        - There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

You have checked the first one, but I would guess not the others.  They are a good guide - the usual three culprits when using PostGres really are that your network is blocking access, the dbconfig.xml is wrong, and the database is not set up to allow you in (much as I love postgres when it's working, I despise the painful command line options and would like to take the "hba" config stuff out and kill it, horribly)

SUPPORT SFCWR · Answer

Hello You find bellow the error in the log file 2018-06-11 00:40:57,454 JIRA-Bootstrap ERROR [c.a.config.bootstrap.DefaultAtlassianBootstrapManager] Could not successfully test your database: org.postgresql.util.PSQLException: The connection attempt failed. at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:272) at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:52) at org.postgresql.jdbc.PgConnection.(PgConnection.java:216) at org.postgresql.Driver.makeConnection(Driver.java:404) at org.postgresql.Driver.connect(Driver.java:272) at java.sql.DriverManager.getConnection(DriverManager.java:664) at java.sql.DriverManager.getConnection(DriverManager.java:247) at com.atlassian.config.bootstrap.DefaultAtlassianBootstrapManager.getTestDatabaseConnection(DefaultAtlassianBootstrapManager.java:347) at com.atlassian.jira.config.database.JdbcDatasource.getConnection(JdbcDatasource.java:211) at com.atlassian.jira.config.database.DatabaseConfig.testConnection(DatabaseConfig.java:88) at com.atlassian.jira.health.checks.DbConfigurationAndConnectionCheck.doPerform(DbConfigurationAndConnectionCheck.java:60) at com.atlassian.jira.health.HealthCheckTemplate.perform(HealthCheckTemplate.java:23) at com.atlassian.jira.health.DefaultHealthCheckExecutor.runCheck(DefaultHealthCheckExecutor.java:74) at com.atlassian.jira.health.DefaultHealthCheckExecutor.lambda$applyAndCollectExceptions$1(DefaultHealthCheckExecutor.java:53) at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175) at java.util.Iterator.forEachRemaining(Iterator.java:116) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151) at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418) at com.atlassian.jira.health.DefaultHealthCheckExecutor.applyAndCollectExceptions(DefaultHealthCheckExecutor.java:53) at com.atlassian.jira.health.DefaultHealthCheckExecutor.performHealthChecks(DefaultHealthCheckExecutor.java:42) at com.atlassian.jira.health.HealthChecks.executeChecksAndRecordResults(HealthChecks.java:164) at com.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:154) at com.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:66) at com.atlassian.jira.startup.BootstrapContainerLauncher.start(BootstrapContainerLauncher.java:48) at com.atlassian.jira.startup.DefaultJiraLauncher.preDbLaunch(DefaultJiraLauncher.java:115) at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:101) at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31) at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:100) at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154) at java.lang.Thread.run(Thread.java:745) Caused by: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at org.postgresql.core.PGStream.(PGStream.java:61) at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:144) ... 35 more 2018-06-11 00:40:57,514 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database 2018-06-11 00:40:57,514 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database. This could be because: - Your database isn't running - The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.) - There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.) There are several other solutions you can try, review our documentation and see what works for you. 2018-06-11 00:40:57,517 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks. 2018-06-11 00:40:57,517 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. JIRA will be locked. 2018-06-11 00:40:57,719 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage: --------------------------------------------------------------------------------- Heap memory : Used: 233 MiB. Committed: 1495 MiB. Max: 1495 MiB Non-heap memory : Used: 37 MiB. Committed: 39 MiB. Max: 1264 MiB --------------------------------------------------------------------------------- TOTAL : Used: 270 MiB. Committed: 1534 MiB. Max: 2759 MiB --------------------------------------------------------------------------------- could you check, do you have an idea how to resolve this? Thank you

Nic Brough -Adaptavist- · Answer

That's a very generic error, taken out of context.

There should be more of it on-screen, but if that really is all you have, you will need to look at the Jira logs in <jira-home>/logs - probably the atlassian-jira.log file.