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; } } }

Upgrade path from Confluence 2.8.3?

unknown

Hello,

We are currently running Confluence 2.8.3 standalone, on Server 2008 R2, on a Microsoft SQL 2008 R2 database and LDAP authentication.

We'd like to upgrade to the latest version of Confluence & run Confluence as a service.

But is the best upgrade path for our installation type?

Thanks,

Daniel

Accepted answers

Amalia

In order to upgrade from 2.8.x to the latest version of Confluence, please perform an intermediary upgrade to 3.5.17. After the upgrade went successfully (and ensuring Confluence works as expected), you will then need to upgrade to the latest version (4.3.x).

Here's the documentation on how to upgrade to 3.5.x: https://confluence.atlassian.com/display/CONF35/Upgrading+Confluence+Standalone+Distribution

and this one is for upgrading to 4.3.x: https://confluence.atlassian.com/display/DOC/Upgrading+Confluence+Manually

All comments

Larry Talley

Having migrated an out-of-date site to Atlassian OnDemand, here is what I did:

Download a number of versions of Confluence to a local PC:

http://www.atlassian.com/software/confluence/download-archives

I am pretty sure you will need all of the major releases, i.e., 3.x, 3.5, maybe 4.0, 4.3. If you can you might want to use 3.1 instead of 3.0, 4.1 instead of 4.0, etc. to minimize problems with the newest releases, but that may not be supported... you may need to read a lot of release notes. I am pretty sure that you have to go through release 3.5 because that was a big release. I am not sure if you can go directly from 2.8.3 to version 3.5 but the release notes should tell you.

Export your current production site in XML format, and be sure to check the "get all pages even those I don't have permission to see".

Once you have all of these downloaded, install the first one that is greater than your curren version, i.e., 3.0.x or 3.1.x. Perform a very basic install on a PC. If it is convenient you may want to point your PC instance at a new database account in the MS SQL database, but, in my experience I was able to use the internal database for these migration steps without problems. BUT -- when the install is complete and it asks if you want to create a new wiki or restore an existing wiki, then you point to the export file from your 2.8.3 version, and the new install should migrate that existing content into your new version 3.x instance on your PC.

Then you export the version 3 instance in XML format and be sure to check the "get all pages" option.

Then you install 3.5.x on your PC and at the last step you point it to the version 3 export file.

Then do the same with version 4 up to 4.3.

You will need to read the release notes to be sure about which versions you may be able to skip. I think that you can always skip the minor releases except for 3.5 which I believe is special.

Finally you will have a version 4.3 XML export that can be imported into Atlassian OnDemand.

Go through the steps to purchase OnDemand and then follow directions at:

https://confluence.atlassian.com/display/AOD/Importing+wiki+data

In my case I did some "grepping" of the xml file to get all the distinct usernames, and similar shenanigans to get groups, and I built a CSV file to establish my users and groups. I no longer recall all of the reasons I did that. It might not be necessary if you have pretty normal user and group situations. In my case I had at least a couple of users that wanted a username change during the process (which I was able to do), and, I wanted to normalize the use of groups for authorization because it had gotten messy over time. But it would be nice to not have to do anything special with users and groups, and the import process may just take care of it.

It sounds kind of ugly but if you make good naming conventions for your export files and keep track of your steps it isn't completely awful.

Amalia

Here's the documentation on how to upgrade to 3.5.x: https://confluence.atlassian.com/display/CONF35/Upgrading+Confluence+Standalone+Distribution

and this one is for upgrading to 4.3.x: https://confluence.atlassian.com/display/DOC/Upgrading+Confluence+Manually

unknown

So I'm attempting to upgrade from 2.8.3 to 3.5.17 as you recommended. I've followed the instructions you've listed (https://confluence.atlassian.com/display/CONF35/Upgrading+Confluence+Standalone+Distribution)

The following appears in the Tomcat window;

Nov 13, 2012 8:12:45 PM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.

Nov 13, 2012 8:12:45 PM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.

Nov 13, 2012 8:12:45 PM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.

Nov 13, 2012 8:12:45 PM org.apache.tomcat.util.digester.SetPropertiesRule begin

WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.

Nov 13, 2012 8:12:46 PM org.apache.coyote.http11.Http11Protocol init

INFO: Initializing Coyote HTTP/1.1 on http-8080

Nov 13, 2012 8:12:46 PM org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 770 ms

Nov 13, 2012 8:12:46 PM org.apache.catalina.core.StandardService start

INFO: Starting service Tomcat-Standalone

Nov 13, 2012 8:12:46 PM org.apache.catalina.core.StandardEngine start

INFO: Starting Servlet Engine: Apache Tomcat/6.0.32

2012-11-13 20:12:51,595 INFO [main] [com.atlassian.confluence.lifecycle] context

Initialized Starting Confluence 3.5.17 (build #2176)

2012-11-13 20:12:57,395 INFO [main] [atlassian.plugin.manager.DefaultPluginManager] init Initialising the plugin system

2012-11-13 20:12:57,712 INFO [main] [atlassian.plugin.manager.DefaultPluginManager] init Plugin system started in 0:00:00.315

(continued in next post)

unknown

(continued)

2012-11-13 20:12:59,724 WARN [main] [atlassian.config.xml.AbstractDom4jXmlConfigurationPersister] saveDocumentAtomically Unable to move E:\confluence-2.8.3-std\confluence\data\confluence.cfg.xml5512878231749498712tmp to E:\confluence-2.8.3-std\confluence\data\confluence.cfg.xml. Falling back to non-atomic overwrite.

Nov 13, 2012 8:13:42 PM org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-8080

Nov 13, 2012 8:13:42 PM org.apache.catalina.startup.Catalina start

INFO: Server startup in 55854 ms

And the website (now on port 8080, not 80) displays the following:

<th>Type</th><th width="40%">Description</th><th width="40%">Exception</th><th>Level</th><th nowrap="nowrap">Time</th>

upgrade

Upgrade failed. Please consult the system logs for details. You will need to fix these problems, restore your database and confluence home directory to the pre upgrade state. Then retry the upgrade.

Your server id is: A6NE-RD6D-C5QJ-XZWA

error

2012-11-13 20:13:38

I've followed the instructions throughly but still recieving errors..

Thanks

unknown

Attempting to Export my space results in the following error message page...

Cause:
org.springframework.transaction.UnexpectedRollbackException: Transaction rolled back because it has been marked as rollback-only
at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:626)
org.springframework.transaction.UnexpectedRollbackException: Transaction rolled back because it has been marked as rollback-only
	at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:626)
	at com.atlassian.xwork.interceptors.XWorkTransactionInterceptor.intercept(XWorkTransactionInterceptor.java:131)

... lots more lines of data, I can post if you like ...

Suggestions?

Thank you

Amalia

The logs that you should be looking is atlassian-confluence.log located in your Home Directory. I would recommend you to raise a new support ticket at https://support.atlassian.com