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 old Confluence 3.4.6

HonWai Wan

Hi support,

I'm upgrading an old Confluence 3.4.6 to the current one. The first step, if I understand, it's to upgrade in the version 3.5.17. I followed the instructions in https://confluence.atlassian.com/display/CONF35/Upgrading+Confluence+Standalone+Distribution, without customization part. But I get a error page in browser, no error in log files. I don't know how I can do.

Error description :
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.

Server configuration : (Migration test server, an exact copy from the production one with VMWare, only server name was changed to acces)

* 3.5.17 standalone
* local postgrest DB
* OpenLDAP authentication

Thanks for your help.

Accepted answers

All comments

Nic Brough -Adaptavist-

"No error in log files" - I'm afraid that simply isn't right. Please check ALL of them, especially the one that definitely says "Upgrade failed" in it.

The only time your log files won't have that in them is if you run out of disk space during the upgrade, so cheeck that first.

HonWai Wan

Hi Nic,

The following log files in <Installation-Directory>/logs :

-rw-r--r-- 1 confluence confluence 49494 Feb 6 16:50 catalina.2014-02-06.log

-rw-r--r-- 1 confluence confluence 61812 Feb 6 16:50 catalina.out

-rw-r--r-- 1 confluence confluence 0 Feb 6 15:21 host-manager.2014-02-06.log

-rw-r--r-- 1 confluence confluence 0 Feb 6 15:21 localhost.2014-02-06.log

-rw-r--r-- 1 confluence confluence 0 Feb 6 15:21 manager.2014-02-06.log

Maybe these aren't the good files ?

Or the problem is before the upgrade process. DB access is maybe not possible. I don't know. Give you the following log lines (in catalina.2014-02-06.log) after the commands startup.sh and shutdown.sh, failed messages are printed when I shutdown the service, but no failed message when I start the service :

=====

Feb 6, 2014 4:07:03 PM org.apache.tomcat.util.digester.SetPropertiesRule begin

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

Feb 6, 2014 4:07:04 PM org.apache.tomcat.util.digester.SetPropertiesRule begin

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

Feb 6, 2014 4:07:04 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.

Feb 6, 2014 4:07:04 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.

Feb 6, 2014 4:07:04 PM org.apache.coyote.http11.Http11Protocol init

INFO: Initializing Coyote HTTP/1.1 on http-8080

Feb 6, 2014 4:07:05 PM org.apache.coyote.http11.Http11Protocol init

INFO: Initializing Coyote HTTP/1.1 on http-8443

Feb 6, 2014 4:07:05 PM org.apache.catalina.startup.Catalina load

INFO: Initialization processed in 2376 ms

Feb 6, 2014 4:07:05 PM org.apache.catalina.core.StandardService start

INFO: Starting service Tomcat-Standalone

Feb 6, 2014 4:07:05 PM org.apache.catalina.core.StandardEngine start

INFO: Starting Servlet Engine: Apache Tomcat/6.0.32

Feb 6, 2014 4:07:41 PM org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-8080

Feb 6, 2014 4:07:41 PM org.apache.coyote.http11.Http11Protocol start

INFO: Starting Coyote HTTP/1.1 on http-8443

Feb 6, 2014 4:07:41 PM org.apache.catalina.startup.Catalina start

INFO: Server startup in 35986 ms

Feb 6, 2014 4:15:56 PM org.apache.coyote.http11.Http11Protocol pause

INFO: Pausing Coyote HTTP/1.1 on http-8080

Feb 6, 2014 4:15:56 PM org.apache.coyote.http11.Http11Protocol pause

INFO: Pausing Coyote HTTP/1.1 on http-8443

Feb 6, 2014 4:15:57 PM org.apache.catalina.core.StandardService stop

INFO: Stopping service Tomcat-Standalone

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [] registered the JDBC driver [org.hsqldb.jdbc.JDBCDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [com.google.common.base.internal.Finalizer] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [QuartzScheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [QuartzScheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [QuartzScheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [QuartzScheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [QuartzScheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [QuartzScheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [QuartzScheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [QuartzScheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [QuartzScheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [QuartzScheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [] appears to have started a thread named [Resource Destroyer in BasicResourcePool.close()] but has failed to stop it. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application [] created a ThreadLocal with key of type [com.atlassian.core.logging.ThreadLocalErrorCollection$2] (value [com.atlassian.core.logging.ThreadLocalErrorCollection$2@6c87ac60]) and a value of type [java.lang.Boolean] (value [false]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application [] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@3f460a4a]) and a value of type [org.dom4j.DocumentFactory] (value [org.dom4j.DocumentFactory@f4da0ba]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

Feb 6, 2014 4:15:57 PM org.apache.catalina.loader.WebappClassLoader clearThreadLocalMap

SEVERE: The web application [] created a ThreadLocal with key of type [org.apache.log4j.helpers.ThreadLocalMap] (value [org.apache.log4j.helpers.ThreadLocalMap@180aa467]) and a value of type [java.util.Hashtable] (value [{}]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

Feb 6, 2014 4:15:58 PM org.apache.coyote.http11.Http11Protocol destroy

INFO: Stopping Coyote HTTP/1.1 on http-8080

Feb 6, 2014 4:15:58 PM org.apache.coyote.http11.Http11Protocol destroy

INFO: Stopping Coyote HTTP/1.1 on http-8443

=====

Thanks for your help.

Theinvisibleman

Hi,

Could you perhaps check the catalina.out log file for errors? Also, what does the error message say?

HonWai Wan

Hi Joe,

Log lines are similare.

catalina.out