The following problems occurred which prevents Atlassian Stash from starting correctly:
Log file says:
2015-07-13 14:34:28,845 ERROR [spring-startup] c.a.plugin.osgi.factory.OsgiPlugin Plugin 'com.atlassian.upm.atlassian-universal-plugin-manager-plugin' never resolved service '&templateRenderer' with filter '(objectClass=com.atlassian.templaterenderer.TemplateRenderer)'
2015-07-13 14:34:28,850 ERROR [spring-startup] c.a.plugin.osgi.factory.OsgiPlugin Plugin 'com.atlassian.webhooks.atlassian-webhooks-plugin' never resolved service '&templateRenderer' with filter '(&(objectClass=com.atlassian.templaterenderer.TemplateRenderer)(objectClass=com.atlassian.templaterenderer.TemplateRenderer))'
2015-07-13 14:34:28,854 ERROR [spring-startup] c.a.plugin.osgi.factory.OsgiPlugin Plugin 'com.atlassian.stash.stash-dev-summary-plugin' never resolved service '&applicationLinkService' with filter '(objectClass=com.atlassian.applinks.api.ApplicationLinkService)'
2015-07-13 14:34:28,854 ERROR [spring-startup] c.a.plugin.osgi.factory.OsgiPlugin Plugin 'com.atlassian.stash.stash-dev-summary-plugin' never resolved service '&jiraKeyScanner' with filter '(objectClass=com.atlassian.integration.jira.JiraKeyScanner)'
2015-07-13 14:34:28,854 ERROR [spring-startup] c.a.plugin.osgi.factory.OsgiPlugin Plugin 'com.atlassian.stash.stash-dev-summary-plugin' never resolved service '&linkedApplicationCapabilities' with filter '(objectClass=com.atlassian.plugins.capabilities.api.LinkedApplicationCapabilities)'
2015-07-13 14:34:28,854 ERROR [spring-startup] c.a.plugin.osgi.factory.OsgiPlugin Plugin 'com.atlassian.stash.stash-dev-summary-plugin' never resolved service '&remoteEventProducerRegistrar' with filter '(objectClass=com.atlassian.event.remote.RemoteEventProducerRegistrar)'
2015-07-13 14:34:28,863 ERROR [spring-startup] c.a.plugin.manager.PluginEnabler Unable to start the following plugins due to timeout while waiting for plugin to enable: com.atlassian.plugins.atlassian-remote-event-common-plugin,com.atlassian.plugins.atlassian-remote-event-producer-plugin,com.atlassian.plugins.atlassian-remote-event-consumer-plugin,com.atlassian.stash.stash-jira-integration,com.atlassian.stash.stash-velocity-helper,com.atlassian.stash.stash-branch-utils,com.atlassian.upm.atlassian-universal-plugin-manager-plugin,com.atlassian.webhooks.atlassian-webhooks-plugin,com.atlassian.stash.stash-dev-summary-plugin,com.atlassian.stash.stash-stp-integration
2015-07-13 14:36:47,209 WARN [spring-startup] c.a.s.i.p.StaticPluginPathScanner Cannot scan directory /static/feature/tasks/icons/ in web static as it does not exist
2015-07-13 14:36:47,372 INFO [spring-startup] c.a.s.internal.scm.PluginScmService Stash is using /usr/bin/git version 2.3.3
2015-07-13 14:36:47,447 INFO [spring-startup] c.a.s.i.hazelcast.HazelcastLifecycle Updating Hazelcast instance capabilities
------
I have followed the link https://confluence.atlassian.com/display/STASHKB/Stash+failed+to+Start+due+to+Required+plugin+failed+to+start (Stash failed to Start due to Required plugin failed to start) which is the nearest error I can find the one I am seeing but this doesn't fix the error.
Appreciate your help!
Thanks
Jim
Support advised we amended a timeout in the setenv.sh file
</usr/atlassian/stash/3.8.1/bin/setenv.sh> Appending the JVM_SUPPORT_RECOMMENDED_ARGS="" Like this …
JVM_SUPPORT_RECOMMENDED_ARGS="-Datlassian.plugins.enable.wait=600"
Which we duly did and this fixed the problem. However this didn't explain why stash was taking so long to startup. Turns out that MacAfee was making the startup so slow - so we stopped MacAffe
#/etc/rc3.d/S92nails stop
Then started stash
#/etc/rc3.d/S50atlstash start (started in seconds)
Started MacAfee
#/etc/rc3.d/S92nails start
Many thanks to Andrew in Support!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
is this issue resolved, i am facing this issue when startup bitbucket image in aws instance
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jim,
That definitely does not look right. Could you raise an issue for our support team to investigate at https://support.atlassian.com (including the logs, as you have above)?
cheers,
Tim
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.