Can someone plz help me out? I am now getting the following error now. I am fighting with this issue all day
2014-03-07 18:39:13,577 INFO [Thread-43] [atlassian.plugin.manager.DefaultPluginManager] shutdown Shutting down the plugin system
2014-03-07 18:39:13,619 INFO [Thread-43] [com.atlassian.confluence.lifecycle] destroy Shutting down long running task service
2014-03-07 18:39:15,496 INFO [Thread-43] [com.atlassian.confluence.lifecycle] contextDestroyed Stopping Confluence
2014-03-07 18:39:21,440 INFO [main] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 5.4.3 [build 4732 based on commit hash f543bd9a3bbc12daed85f6f5e5cba84282599932]
2014-03-07 18:39:23,996 INFO [main] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization started
2014-03-07 18:39:27,682 INFO [main] [com.atlassian.confluence.lifecycle] <init> Loading EhCache cache manager
2014-03-07 18:39:39,855 WARN [main] [org.springframework.beans.TypeConverterDelegate] findDefaultEditor PropertyEditor [com.sun.beans.editors.EnumEditor] found through deprecated global PropertyEditorManager
2014-03-07 18:39:48,213 INFO [main] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization completed in 24217 ms
2014-03-07 18:39:48,603 ERROR [main] [atlassian.confluence.setup.BootstrapApplicationStartupListener] checkConfigurationOnStartup Detected tables with non-default collation. Seehttps://confluence.atlassian.
2014-03-07 18:39:48,842 WARN [main] [atlassian.confluence.plugin.PluginFrameworkContextListener] contextInitialized Not starting full plugin system due to upgrade or licensing errors
2014-03-07 18:39:50,621 INFO [main] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve
Hi Samar,
As pointed in the stacktrace, the cause of this issue is probably incorrect collation
2014-03-07 18:39:48,603 ERROR [main] [atlassian.confluence.setup.BootstrapApplicationStartupListener] checkConfigurationOnStartup Detected tables with non-default collation. Seehttps://confluence.atlassian.
Since this error occur after the ugparde process, I suspect that the upgrade might not have completed properly due to the incorrect. The upgrade process for newer version of Confluence is much more sensitve toward the wrong collation therefore if you have incorrect collation in the database the upgrade will fail.
It is best that you rollback to your pre upgrade state, then change your collation as mentioned in this KB. After that perform the upgrade again.
Regards,
Jing Hwa
Yes, the new confluence is sensitive.. that i realize NOW. It was indeed the Character Encoding or Collation Issues in MySQL. Thanks Jing, its resolved now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
They fixed the character encoding, as given in the doc at the time. It was 4 years ago and the doc has moved to https://confluence.atlassian.com/confkb/how-to-fix-the-collation-and-character-set-of-a-mysql-database-670958160.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Samar,
Don't worry we are here to help.
Check the permission of the directory and grant writable permission to your directory. I would also recommend you to clear the plugin cash.
Cheers,
Saleh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.