I'm very new to Confluence. But I think I'm going to like it.
After the upgrading process from 3.5.9 to 5.0.3 to 5.4.4 there are still some errors left in my log on startup. I just wanted to ask some of our experts to take a short look into my log-file. I'd appriciate every help very grateful.
Here is, how i did the upgrade (of course I did backups)
- Disabled all incompatible plugins in 3.5.9
- Full Backup
- Upgraded from 3.5.9 to 5.0.3 (cleared plugin caches)
- Full Backup 5.0.3
- Upgraded from 5.0.3 to 5.4.4
- Enable most of pre-disabled Plugins which were compatible
But now some errors occur during startup. I hope someone can help me out.
This is my startuplog:
I found following stack traces in your new Log file:
2014-04-24 11:17:53,936 ERROR [Timer-4] [extender.internal.activator.ContextLoaderListener] onOsgiApplicationEvent Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.confluence.plugins.confluence-profile, config=osgibundle:/META-INF/spring/*.xml)) org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.confluence.plugins.confluence-profile' has timed out at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:454) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:50) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:105) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505) 2014-04-24 11:17:53,936 WARN [Timer-4] [internal.dependencies.startup.DependencyWaiterApplicationContextExecutor] timeout Timeout occurred before finding service dependencies for [NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.confluence.plugins.confluence-profile, config=osgibundle:/META-INF/spring/*.xml)] 2014-04-24 11:17:53,936 ERROR [Timer-4] [internal.dependencies.startup.DependencyWaiterApplicationContextExecutor] fail Unable to create application context for [com.atlassian.confluence.plugins.confluence-profile], unsatisfied dependencies: Dependency on [(objectClass=com.atlassian.confluence.plugins.avatar.ImageHelper)] (from bean [&imageHelper]), Dependency on [(objectClass=com.atlassian.confluence.plugins.avatar.AvatarManager)] (from bean [&avatarManager]), Dependency on [(objectClass=com.atlassian.confluence.plugins.avatar.AvatarUrlHelper)] (from bean [&avatarUrlHelper]) org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.confluence.plugins.confluence-profile' has timed out at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:454) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:50) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:105) at java.util.TimerThread.mainLoop(Timer.java:555) at java.util.TimerThread.run(Timer.java:505)
It's similar to this KB. I would like to recommend you to take a look at our KB for workaround of this issue.
Let me know if you have any other questions.
just did the recommended steps. Further i enabled the "Confluence Profile" and now it seems that this specific error has gone.
Thank you for your help. I am very grateful for the quick help.
Now there's only one ERROR left, but that's arsenale-lockpoint specific.
Well, it's time now... I have another question.
This was upgraded in our Test Environment. I think now it is running almost stable and without that huge amount of errors as before.
But: Our Production Environment is planned to upgrade soon.
So... is it better to deinstall all plugins (as Scott recommended now in 5.4.4) , which are not included into confluence before upgrading from 3.5.9 to 5.0.3 to 5.4.4 ?
Or... should I just disable all of them and try to upgrade and then enable them again?
Which are the best practises to do such an big jump to these version?
I followed the instructions from the help- and howto-pages so far.
Thanks in advance!
I went through your first log file quickly and I found following stack traces:
2014-04-23 13:09:34,272 ERROR [main] [confluence.plugin.descriptor.AbstractExtractorModuleDescriptor] createModule Plugin module com.atlassian.confluence.plugins.socialbookmarking:bookmarkExtractor is incompatible with this version of Confluence. You will need to upgrade to a newer version of the Social Bookmarking Plugin plugin.
Above stack trace shows that Social Bookmarking Plugin is incompatible with your current version.
2014-04-23 13:08:26,599 ERROR [main] [plugin.osgi.factory.UnrecognizedModuleDescriptorServiceTrackerCustomizer] canFactoryResolveUnrecognizedDescriptor Unable to transform de.five1.confluence.abapsyntax:abap into actual plugin module using factory com.atlassian.plugin.schema.impl.DefaultDescribedModuleDescriptorFactory@4ff133e5 org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.atlassian.renderer.v2.macro.code.SourceCodeFormatterModuleDescriptor': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [com.atlassian.renderer.v2.macro.code.SourceCodeFormatterModuleDescriptor]: Constructor threw exception; nested exception is java.lang.NoSuchMethodError: com.atlassian.plugin.descriptors.AbstractModuleDescriptor: method <init>()V not found at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:883) .. at com.atlassian.plugin.osgi.factory.UnrecognizedModuleDescriptorSer
Above error is related to your ABAP Code Formatter. As you can see it's in your Enable Plugins section:
ABAP Code Formatter (de.five1.confluence.abapsyntax, Version: 1.0, Installed: Oct 12, 2011)
As you want to perfom upgrade in your production instance, I would like to recommend you to perform upgrade from 5.0.3 in your test instance again but disable these two plugins first this time and check your log files again. If the issue presists after disabling these two plugins you might need to check for the other incompatible plugins or following Rodrigo's recommendation. Otherwise you can perform upgrade without these two plugins.
The no such method error is known to happen when there's a corruption in the plugin system and/or there is one or more plugins incompatible with the current version of confluence.
I recommend to create a list of all third party plugins in confluence and remove all plugins from the system using the commands here.
Also, while confluence is down, run a delete SQL to clear the plugindata table and remove the third party plugins. Always backup the database before running any delete or update command.
delete from plugindata;
Then restart confluence and all third party plugins should be gone. You now just have to reinstall the necessary plugins again and download the latest compatible version of each plugin.
If you are still seeing the Lockpoint error in the log after your restart, contact Arsenale Support at http://www.arsenalesystems.com/support. They should look into the second-last line in the log segment above.
PS: This is probably not related to the error, but your log indicates that you are using Java 6. Note that Confluence 5.4 requires at least Java 7. You might want to look into upgrading your JRE soon as well.
thank you very much. I did just the upgrade to JDK 1.7. But still getting the same ERRORs. I sent the LOG-lines you requested to your given link above.
Thanks for your help!
After installing the Arsenale Plugin and restarting the server, error occured again:
2014-04-24 11:55:42,706 INFO [main] [com.atlassian.confluence.lifecycle] init Confluence is ready to serve
2014-04-24 11:55:43,486 ERROR [main] [arsenale.plugins.lockpoint.StartupAndShutdown] init Code 302: com.arsenale.plugins.lockpoint.TTPNFE: Code 100: FRaJxiS2LHPwB0G0Vrh/Zz1MDRWzPQs/ZgnhqLKbzKGXLoViqAZRbDuEFGkoi7q2ATXsItfs8v0V683Y9Sm92g==
2014-04-24 11:55:43,642 INFO [lockpointActionThread:thread-1] [atlassian.plugin.manager.DefaultPluginManager] notifyPluginDisabled Disabling confluence.sections.attachments
2014-04-24 11:55:47,043 WARN [scheduler_Worker-9] [gadgets.renderer.internal.GadgetSpecFactoryImpl] getGadgetSpec Error occurred while retrieving gadget spec for http://www.doodle.com/opensocial/gadget.xml
Thank you for your submission. We just sent you an email response. We will work with you through our support tracker to figure it out, but we will post the resolution here when everything is done in case anyone else is tracking this thread.
For the sake of anyone else who is following this thread:
We were able to diagnose Mario's issue. It turns out that they had modified one of the Confluence system Velocity files in $CONFLUENCE_INSTALL/confluence/pages/includes/*.vm. Lockpoint needed to work with the contents of the same file, but the modifications prevented Lockpoint from finding what it needed.
We've supplied guidance on what is safe and what should be avoided in modifications of those files, so they now know how to solve the problem.
For the sake of other arrivees from Google: the same symptoms and a similar error message could appear in the logs if you try to use a version of Lockpoint that is not compatible with the installed version of Confluence. That was not the case here, since Mario is using Lockpoint 1.5.3 with Confluence 5.4.4, which is definitely supported...but it is always a good idea to check the Lockpoint system requirements and the Confluence compatibility version matrix first.
Just did the two steps:
- Upgrade to JDK1.7
- Clearing Pluginscache and DB-DELETE
This is the new StartupLog:
Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...
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!
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