Confluence Upgrade from 4.1.7 to 4.2.1 failed

Question

We ran the upgrade script to upgrade from 4.1.7 to 4.2.1. There was no error during the execution of the script, but afterwards we are just getting an upgrade failed message when we attempt to access Confluence. We also don't see any failure message in the log.

Apr 24, 2012 1:01:19 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8090
Apr 24, 2012 1:01:23 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not fi$
Apr 24, 2012 1:01:23 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to$
Apr 24, 2012 1:01:23 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debu$
Apr 24, 2012 1:01:23 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting proper$
Apr 24, 2012 1:01:23 PM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8090
Apr 24, 2012 1:01:23 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 266 ms
Apr 24, 2012 1:01:23 PM org.apache.catalina.core.StandardService start
INFO: Starting service Tomcat-Standalone
Apr 24, 2012 1:01:23 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.32
2012-04-24 13:01:24,156 INFO [main] [com.atlassian.confluence.lifecycle] contex$
alter table CONTENT_LABEL add column ATTACHMENTID bigint
Apr 24, 2012 1:01:41 PM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8090
Apr 24, 2012 1:01:41 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 18545 ms

How can we fix it? Is there an easy way to downgrade?

Thanks!

Bruna Griebeler · Answer

Hello!

I believe that you paste the catalina.out output, so I suggest you to search on <HOME-DIRECTORY>/logs/atlassian-confluence.log for ERRORS related to upgrade.

It might be something related to plugins so before performing the upgrade is important to check for compatible plugins before.

You can find more information  on this link

If the problem persists you can open a ticket on support.atlassian.com for more information.

Regards!

Seth Floyd · Answer

I am seeing something similar to this as well.

I think the key to the issue is the alter that is in the log output above. We get hung on something similar as well and we are going from 4.1.4 to 4.2.11. Im waiting on my dba to roll back to our backup from last night as i write this.

In order to roll back to a working state you can copy the confluence dir from the zip file thats created during the upgrade back to where it originally was and then roll back your db from your backup. You did make backups right? :)

I havent figured out the exact issue or how to get a successful upgrade but when i do i will come back to let you know exactly what I did.