Confluence Upgrade 5.6.6 to 5.7 fails

After upgrading Confluence from 5.6.6 to 5.7 we're getting the message

confluence error.JPG

Any idea what's happening?

Regards

Johannes.

 

2 answers

This widget could not be displayed.

Yes, it means your upgrade has failed and you need to revert to the backup you took before you ran the upgrade.

Preserve the log files before you roll back - you will want to read them to find out why the upgrade failed.

In which Directory will I find the respective log file?

Unless you have reconfigured it, you will find it under the "home directory" you set for confluence, beneath /logs Should be called atlassian-confluence.log

I can find these SEVERE errors in a log-file: wrong JDBC-Driver? 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 26, 2015 4:19:44 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 26, 2015 4:19:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc SEVERE: The web application [] registered the JDBC driver [net.sourceforge.jtds.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 26, 2015 4:19:44 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads SEVERE: The web application [] appears to have started a thread named [Statistics Thread-__DEFAULT__-1] but has failed to stop it. This is very likely to create a memory leak.

Hmm, well, that is a problem, but it's an issue as the server is shutting down - you need to concentrate on the upgrade errors.

This widget could not be displayed.

Hi Johannes,

The Atlassian-confluence.log files should have a more detailed information on the upgrade failure. If you are unable to pinpoint the reason why the upgrade failed in the logs, I suggest to get in touch with the Atlassian support so we can investigate the root cause.

Cheers,

Rodrigo

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Monday in Confluence

Why start from scratch? Introducing four new templates for Confluence Cloud

Hi my Community friends!  For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...

487 views 6 6
Join discussion

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