Cannot proceed with upgrade. Cluster upgrade lock acquired but could not successfully tag build number in the CONFVERSION table

While upgrading Confluence 5.3.1 to 5.4, I'm gettting following error. I'm using Mysql 5.1.71-community version and java 1.7.0_25. Here's the full stack trace of exception:

[TEAM]: ERROR 02 May 2014 17:34:32,093 [main] com.atlassian.confluence.upgrade.UpgradeLauncherServletContextListener "Upgrade failed, application will not start: com.atlassian.confluence.upgrade.UpgradeException: Cannot proceed with upgrade. Cluster upgrade lock acquired but could not successfully tag build number in the CONFVERSION table. This may because you are trying to rerun an upgrade that has failed or there are communication problems between one or more nodes in your cluster. Please zip up your logs and attach onto a support ticket at http://support.atlassian.com."

com.atlassian.confluence.upgrade.UpgradeException: com.atlassian.confluence.upgrade.UpgradeException: Cannot proceed with upgrade. Cluster upgrade lock acquired but could not successfully tag build number in the CONFVERSION table. This may because you are trying to rerun an upgrade that has failed or there are communication problems between one or more nodes in your cluster. Please zip up your logs and attach onto a support ticket at http://support.atlassian.com.

at com.atlassian.confluence.upgrade.AbstractUpgradeManager.runUpgradeTasks(AbstractUpgradeManager.java:222)

at com.atlassian.confluence.upgrade.AbstractUpgradeManager.upgrade(AbstractUpgradeManager.java:159)

at com.atlassian.confluence.upgrade.UpgradeLauncherServletContextListener.contextInitialized(UpgradeLauncherServletContextListener.java:50)

at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)

at org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)

at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)

at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)

at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)

at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)

at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)

at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)

at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)

at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)

at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)

at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)

at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)

at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)

at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)

at org.apache.catalina.core.StandardService.start(StandardService.java:525)

at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)

at org.apache.catalina.startup.Catalina.start(Catalina.java:595)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

Caused by: com.atlassian.confluence.upgrade.UpgradeException: Cannot proceed with upgrade. Cluster upgrade lock acquired but could not successfully tag build number in the CONFVERSION table. This may because you are trying to rerun an upgrade that has failed or there are communication problems between one or more nodes in your cluster. Please zip up your logs and attach onto a support ticket at http://support.atlassian.com.

at com.atlassian.confluence.upgrade.impl.DefaultUpgradeManager.permitDatabaseUpgrades(DefaultUpgradeManager.java:239)

at com.atlassian.confluence.upgrade.AbstractUpgradeManager.initialUpgradeFinished(AbstractUpgradeManager.java:480)

at com.atlassian.confluence.upgrade.impl.DefaultUpgradeManager.initialUpgradeFinished(DefaultUpgradeManager.java:190)

at com.atlassian.confluence.upgrade.AbstractUpgradeManager.runUpgradeTasks(AbstractUpgradeManager.java:217)

... 26 more

1 answer

1 accepted

0 votes
Answer accepted

Hi Niraj,

It seems like the CONFVERSION table was already updated during a previous failed upgrade attempt.
Please take a look at this KB for possible resolutions:

https://confluence.atlassian.com/display/CONFKB/Confluence+will+not+start+up+because+the+build+number+in+the+home+directory+doesn%27t+match+the+build+number+in+the+database,+after+upgrade



Kind Regards

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 12, 2019 in Confluence

Confluence Admin Certification now $150 for Community Members

More and more people are building their careers with Atlassian, and we want you to be at the front of this wave! Important Dates Start the Certification Prep Course by 2 April 2019 Take your e...

274 views 2 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you