Confluence had failed to start

[Rajratan Dahane]

Hi Team,

we have installed the service ,but when we are trying to access the site getting an error
'Confluence had failed to start, but we're back up and running again'

PFA below

could you please suggest the solution ,is there anything that we missed?

this issue is occur only when we are connected to Prod database.

But when we are connected to QA database we are able to access the site.

[Rajratan Dahane]

Hi Team,

we are getting following screen while accessing confluence site.

following is the Home Log.

could you please suggest any solution for that

2018-04-26 02:34:00,038 INFO [synchrony-interop-executor:thread-1] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] debugPrintEnvironment C:\Progra~1\Java\jre1.8.0_60\bin\java.exe -classpath G:\data\inetpub\Confluence\Confluence670\Std\temp\2.1.0-release-confluence_6.5-1a01ab2d.jar;G:\data\inetpub\Confluence\Confluence670\Std\confluence\WEB-INF\lib\jtds-1.3.1.jar -Xss2048k -Xmx1g synchrony.core sql
2018-04-26 02:34:00,270 INFO [ListenableFutureAdapter-thread-17] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] isSynchronyProxyEnabled proxy port present: true
2018-04-26 02:34:00,286 INFO [ListenableFutureAdapter-thread-17] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony External Base URL: http://gadc-wikiprd01.na.pg.com:8092/synchrony,http://gadc-wikiprd01.na.pg.com:8092/pages/synchrony-proxy
2018-04-26 02:34:00,286 INFO [ListenableFutureAdapter-thread-17] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony External Service URL: http://gadc-wikiprd01.na.pg.com:8092/synchrony/v1
2018-04-26 02:34:00,286 INFO [ListenableFutureAdapter-thread-17] [plugins.synchrony.bootstrap.DefaultSynchronyProcessManager] updateSynchronyConfiguration Synchrony Internal Service URL: http://127.0.0.1:8092/synchrony/v1
2018-04-26 02:34:00,287 WARN [ListenableFutureAdapter-thread-16] [plugins.synchrony.config.DefaultSynchronyConfigurationManager] enableSharedDrafts [Collab editing plugin] Enabling Shared Drafts

[Nic Brough -Adaptavist-]

There is no error in that log, you will need to read all of it.

[Rajratan Dahane]

yes i know.. but why we are getting the error while accessing the confluence site

[Nic Brough -Adaptavist-]

Because Confluence is not running properly.  It's not able to upgrade, so it's stopped.  You need to read the logs in full to find out why the upgrade has failed.

[Nic Brough -Adaptavist-]

Please tell me you are not connecting one Confluence to two different databases?

You have a production Confluence and a QA one that are totally separate installations?

[Rajratan Dahane]

Hi Nic,

Q:- Please tell me you are not connecting one Confluence to two different databases?

Ans:- we are trying to connect one database at a time(either QA or Pord).
when we are connecting to QA it is working fine.
but when we are trying to connect to Prod database we are getting above error.

Q:-You have a production Confluence and a QA one that are totally separate         installations?     

Ans:- Yes we have 2 different installation.

following is the Confluence-cfg.xml file

[Nic Brough -Adaptavist-]

Those two answers directly contradict each other,

Please.  Do you have two separate Confluence installations, one pointed at the QA database, and the other Production ?

[Rajratan Dahane]

we have ConfluenceQA on different QA server and production is on different server.
both are not on same server

[Nic Brough -Adaptavist-]

So, the QA system works, but the production one fails?

So we can ignore the QA one completely?

[Rajratan Dahane]

yes..

Actually we have installed on production but giving QA Db connection string then it is working fine.
but when are changing prod DB connection string  in server.xml with same installation
giving an error.

[Nic Brough -Adaptavist-]

Do NOT do that.  You can not run two Confluences against one database (Unless we're talking Data Centre, but that's a different case, and it wouldn't

Even if you take QA offline first, then it will let you start Production, but it's going to go wrong in interesting ways (fixable, but you'll have to fix it again when you swap back to QA)

I strongly recommend forgetting QA, leave it alone.  Use the Production Server and the Production database and debug that properly.

What is the error message?

[Rajratan Dahane]

Hi,

do we need to install the new service for production?

following error is getting

[Nic Brough -Adaptavist-]

This warning you're getting is because it failed start up (probably because your installation mismatched the database), but restarting has fixed it and it's now working.

You need to have a good look at the logs to work out what is going on.

[Rajratan Dahane]

Hi Nic,
we have restarted the service and when we are trying to access the site it's showing blank page but not the error page
could you please suggest any solution?

[Nic Brough -Adaptavist-]

What does the application log say it is doing?  <confluence home>/logs/atlassian-confluence.log (and a look at other files in there)

[Rajratan Dahane]

Hi Nic,

We have installed new service on production server with Prod DB connection.
but when we are trying to access through locally and remotly we are getting an error 404 
I am attaching error screen shot.

could you please suggest the solution 

[Nic Brough -Adaptavist-]

Sorry, I missed the reply before.  That tells us Confluence is not running there, you need to check that it is located correctly and that it is running.