nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

upgrading from 7.13.7 to 7.19.5 causes build number error

Vincent voisin

Hi all,

I run a disconnecting (from internet) environment on Docker and I would like to perform an upgrade of my datacenter confluence from 7.13.7 to 7.19.5.

Here my configuration :

- docker nginx 1.22.1-alpine

- docker postgresql 12-alpine

- docker confluence 7.13.7-jdk11

Here my steps to perform this upgrade :

- perform a backup of my database and my data in confluence with a bash script

- stop my docker containers

- backup all my persistant volume

- rm all my volume

- modify my docker-compose to use the new confluence image 7.19.5-jdk11

- restart my docker containers

- check that all is running

- stop my docker containers

- restore my database and my confluence data

- start my docker containers

- go on confluence

then the error appear which says : Confluence will not start up because the build number in the home directory [8804] doesn't match the build number in the database [8703]

So I've followed this link and use the resolution 2 :Confluence will not start up because the build number in the Home Directory doesn't match the build number in the Database, after upgrade | Confluence | Atlassian Documentation
But the problem still here.

Did someone have had this problem before ?

Thanks a lot

Accepted answers

Fabio Racobaldo _Catworkx_

Hi @Vincent voisin and welcome,

did u try to edit build number in your confluence.cfg.xml file adding value 8703?

confluence-configuration>
  ...
  <buildNumber>8703</buildNumber>
  ...
</confluence-configuration>

What happened after doing that?

Fabio

All comments

Fabio Racobaldo _Catworkx_

Hi @Vincent voisin and welcome,

did u try to edit build number in your confluence.cfg.xml file adding value 8703?

confluence-configuration>
  ...
  <buildNumber>8703</buildNumber>
  ...
</confluence-configuration>

What happened after doing that?

Fabio

Vincent voisin

Hi @Fabio Racobaldo _Catworkx_,

Thanks for your answer and your welcome
I've tried this before like it's said in the confluence support page, but, nothing changed.

For now we are trying another solution.
We downgraded our database to PSQL 11 and after this we succeeded to upgrade our confluence to 7.17, but we are stuck again. We need to upgrade to PSQL12 and it failed. It seems that maybe we have a bug in our database.

I let you know as soon as I have more info to communicate, maybe today or tomorrow.

Vincent

Vincent voisin

Hi @Fabio Racobaldo _Catworkx_

Thanks again for your help, here how we resolve our issue :

- downgrade our psql from version 12 to 11

- upgrade confluence from 7.13.7 to 7.17.1

- upgrade psql from version 11 to 14.6

- upgrade confluence from 7.17.1 to 7.19.5

it's the only solution who work for us. We've tried modifying the confluence.cfg.xml, but nothing change. After some research we've found that 7.13.7 doesn't really work with psql 12, so we've decided to downgrade it and apply all of this.

have a nice day,

Vincent

Fabio Racobaldo _Catworkx_

Hey @Vincent voisin , thanks for sharing

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

server

confluence-server

upgrade

docker