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 from Confluence 3.0.1 to latest version

Paul Anderson2

We are currently running Confluence 3.0.1 on Windows Server 2003 R2 with a Microsoft SQL database. We would like to upgrade to the newest version.

First Question:

From looking around the site there may be some benefit to running on Linux with a MYSQL database. Is there any additional functionality included when running on Linux vs. Windows?

Second Question:

Could you provide me a upgrade path for upgrading from Confluence 3.0.1 to 4.2.12. I have looked through readme’s and release notes and it talks about making sure you do all proceeding steps. I would like a list of each version that is required so that I can upgrade with the least amount of effort and downtime.

Accepted answers

All comments

AlysonA

Hello Paul,

For the first question, actually there isn't a recommended OS to run Confluence with MySQL, it should work just fine with both OS's. Just be sure that your configuration meets our supported platforms.

For the second question, the recommended upgrade path would be 3.0.1 > 3.4.9 > 3.5.17 > 4.2.12

Hope that helps!

Jason Hensler1

Why does the upgrade path include 3.4.9? The upgrade guide for 3.5.17 says you can upgrade from 2.7.4 or above to 3.5.17.

AlysonA

Hi Jason,

You're correct, I included the 3.4.9 version because it will help avoiding some user management issues in case you're running Confluence with LDAP. But you can give it a shot and try going straight to 3.5.17 on a test server if you wish.

Jason Hensler1

Gotcha, that is important to know.

Paul Anderson2

Well my upgrade in test is mostly complete. The upgrade to 3.4.9 went fine. The upgade to 3.5.17 had (go figure) LDAP problems. I *think* i caused part of the problems because on the first start after the upgrade it complained about a line of my ldap config in the error because the upgrade complained about the securityprincipal line in the atlassian-user.xml config. I commented the line. The upgrade completed but I had to setup LDAP under 3.5.17. (It probably would have imported it if I would have fixed and not commented it). The upgrade to 4.2.12 is complete but I can not get any plugins to updated they just get stuck at "Installing plugin....." I am just trying to update the Univeral plugin manager first. I at first tried it via update and now I tried it by using the upload plugin option. Both acted the same. If i look at my Tomcat forground log I see these messages over and over:

Aug 17, 2012 2:58:23 PM com.sun.jersey.server.impl.application.WebApplicationImpl _initiate INFO: Initiating Jersey application, version 'Jersey: 1.8-atlassian-6 03/12/2012 02:59 PM'

The java process memory keeps increasing. I keep killing the server because it seems to be taking WAY to long.

None of the logs seems to shed any light.

Any ideas?

Jason Hensler1

Paul,

I had plugin troubles too when I rolled my upgrade. I disabled all the plugins and followed the step on this question https://answers.atlassian.com/questions/56877/why-space-directory-is-blank to clear the plugin-cache dirs. When I did that I backed up the folders listed there first but, I didn't loose any of the installed plugins or anything else for the matter.

AlysonA

Paul,

Jason's suggestions seems to be reasonable, you can give it a try. In case you continue experiencing issues, feel free to raise a support ticket at https://support.atlassian.com so we can continue troubleshooting this issue there.