All front-end and admin pages stay empty. Restarting Jira does not resolve the issue.
The following messages appear in the logs:
Failed to run performUpgradesUnsafe tasks from factory com.atlassian.servicedesk
io.atlassian.util.concurrent.LazyReference$InitializationEception: java.lang.RuntimeException: Could not find upgrade task with OSGi service name com.atlassian.servicedesk.plugins.cannedresponses.internal.bootstrap.upgrade.tasks.AUT_0010_TurnOnCannedResponses
IRA-EventThread-5 ERROR anonymous 1011x212x1 xh8jdh 172.105.68.41 /rest/remote-event-consumer/latest/events/JiraPullRequestEvent [c.a.s.internal.util.SafeRunner] Unable to run event handler issueChangedEvent
java.lang.NullPointerException
at com.atlassian.servicedesk.bootstrap.listener.IssueChangedEventHandler.handleIssueChangedEventSync(IssueChangedEventHandler.java:146)
at com.atlassian.servicedesk.bootstrap.listener.IssueChangedEventHandler.processIssueChangedEvent(IssueChangedEventHandler.java:113)
at com.atlassian.servicedesk.bootstrap.listener.EventListenerLauncher.lambda$onIssueChangedEvent$1(EventListenerLauncher.java:107)
at com.atlassian.servicedesk.internal.util.SafeRunner.runAlways(SafeRunner.java:58)
at com.atlassian.servicedesk.bootstrap.listener.EventListenerLauncher.onIssueChangedEvent(EventListenerLauncher.java:106)
...
@Daniel Ebers thank you for your response and your help.
Last week I already checked the pluginstate in the database. This couldn´t solve the problem. As already mentioned only installing Jira Software and Jira Service Management without any other Plugins also didn´t work.
This morning I tried a different way and could solve the problem for us. After the upgrade last week the plugins "Atlassian Troubleshooting and Support Tools" and "Insight Plugin" were disabled. Today I enabled both and restarted Jira. Now everything is working again. Even we are not running Jira Service Management Data Center, it seems like Insight needs to be enabled before starting Jira.
Regards,
Michael
Thank you very much Michael, you saved the day!
After I enabled Insight Plugin and restarted JSM was able to start!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Venorcis + @Michael Korte
there is a similar thread in Community which at least mentioned the same error message and with the help of Atlassian it seems to have been tracked down to disabled Apps:
Both of you could double check if this is also applying to your instance but if not it might make sense to swiftly contact Atlassian Support so with providing them a support ZIP a more deeper analysis can be done - this is something where Community members are a bit more unlikely to suggest a solution as the details of your server/system are unknown to the Community.
Regards,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are having the same problem after upgrading to Jira Service Management 4.19.0.
Are there any solutions yet? Jira Service Management is not usable anymore, which represents a critical bug for us.
Tried this (https://confluence.atlassian.com/jirakb/installing-jira-software-or-service-management-while-jira-core-is-running-fails-with-jira-software-service-management-is-currently-unavailable-this-might-be-because-an-upgrade-task-has-failed-to-run-or-has-not-yet-completed-973502897.html) already, but also with only Jira software and Jira service management installed the error occurs mentioned by @Venorcis.
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.