Confluence had failed to start, but we're back up and running again

JS
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 1, 2018

I am using Docker https://hub.docker.com/r/atlassian/confluence-server/ and my current version is 6.11.0.

I am trying to upgrade it to the latest version and it fails with the error

Confluence had failed to start, but we're back up and running again

I have a starter license and unfortunately, Atlassian does not give any support for it. I have no way to ask how to fix this error.

Is there any way to debug this?

I have rolled back to 6.11.0 docker image, since I have backup of the data and it works fine.

1 answer

0 votes
Reg Hawkins September 1, 2018

look in the docker logs

and confluence logs https://confluence.atlassian.com/doc/audit-log-829076528.html

Jagat Singh September 1, 2018

Thanks for your reply.

I cannot go to Audit logs as it is stuck at

Finishing up checks

This never finishes

 

In the docker logs, I can see the below message


02-Sep-2018 02:27:54.736 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 29174 ms

 

In the atlassian-confluence.log I can see the following exception, I am not sure how to fix this error.

Caused by: java.lang.IllegalStateException: Unable to create a tracker when osgi is not running


2018-09-02 02:27:54,005 ERROR [localhost-startStop-1] [atlassian.confluence.setup.BootstrapApplicationStartupListener] checkConfigurationOnStartup Confluence will not start up because the build number in the home directory [7801] is newer than the Confluence build number [7500].

 

I checked confluence.cfg.xml it has build number 7801, but I am not sure how Conflunce build number is coming as 7500?

Like Rob Smith likes this
Jagat Singh September 2, 2018

I tried that, confluence is very intelligent and now it gives this error

2018-09-02 22:48:44,114 ERROR [localhost-startStop-1] [atlassian.confluence.setup.BootstrapApplicationStartupListener] checkConfigurationOnStartup Confluence will not start up because the build number in the home directory [7500] doesn't match the build number in the database [7801].

So the original question is still there.

If database has version 7801

Local config has version 7801

From where the Confluence build number 7500 is coming?

I have pulled the latest image, I am trying to find why it coming as

contextInitialized Starting Confluence 6.5.0-m22 [build 7500 based on commit hash 3491a451877d7224c150ad240ad6812920efe2ee] - synchrony version 2.1.0-release-confluence_6.5-6e195ff4

 

Is there any reason that `latest` tag version and version 6.11.0 has size difference for the image

https://hub.docker.com/r/atlassian/confluence-server/tags/

latest

646 MB

6.11.0

634 MB

Something can be wrong in this latest image?

Can someone from Confluence confirm the docker image versioning and size question above?

Jagat Singh September 3, 2018

@Reg Hawkinsdo you know, how the title for the question above got changed?

It seems, someone marked it as solved. But, it is not.

Thanks for your help.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events