getting Error 500, after Universal Plugin Manager update on Jira-8

[Dhavval Aarya]

Error Logs:

Technical details

Log's referral number: 5daf84bb-6120-473f-8622-2aa575991651

Cause

Referer URL: Unknown

java.lang.RuntimeException: javax.servlet.ServletException: java.lang.RuntimeException: javax.servlet.ServletException: java.lang.IllegalArgumentException: Root page 'com.atlassian.jira.gadgets:dashboard-page' does not exist!

java.lang.RuntimeException: javax.servlet.ServletException: java.lang.RuntimeException: javax.servlet.ServletException: java.lang.IllegalArgumentException: Root page 'com.atlassian.jira.gadgets:dashboard-page' does not exist!
	at com.atlassian.web.servlet.plugin.DynamicAuthorizationServletForwarder.forward(DynamicAuthorizationServletForwarder.java:55) [?:?]
	at com.atlassian.web.servlet.plugin.SanitizingServletForwarder.forward(SanitizingServletForwarder.java:32) [?:?]
	at com.atlassian.web.servlet.plugin.RememberingServletForwarder.forward(RememberingServletForwarder.java:51) [?:?]
	at com.atlassian.web.servlet.plugin.ResolvingServletForwarder.forward(ResolvingServletForwarder.java:36) [?:?]
	at jsp.default_jsp._jspService(default_jsp.java:68) [classes/:?]
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) [jasper.jar:8.5.42]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) [servlet-api.jar:?]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) [catalina.jar:8.5.42]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:8.5.42]
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) [tomcat-websocket.jar:8.5.42]
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) [catalina.jar:8.5.42]
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) [catalina.jar:8.5.42]
	at 

[Daniel Ebers · Accepted solution]

Hi Dhavval,

I used to see this error as long as UPM upgrade has not been finished. In case it should stay in this state for more than a few minutes a restart of Jira should fixed the inconvenience.

Cheers,
Daniel

[Michael Benz]

A reboot solved the issue for us when we updated UPM 5.0.5 -> 5.1.5 on a JIRA Server 8.19.1 instance. After the reboot all the disabled core modules like greenhopper have been automatically started again. Also the new UPM 5.1.5 Addon seems to have successfully installed itself.

The UPM manager before stalling or crashing during installation had disabled them and somehow got stuck in the process.

[Sebastian Mendel]

https://jira.atlassian.com/browse/JSWSERVER-15815