How do I diagnose a "Something went wrong" error?

[Bruce Mohler]

I'm getting 3 "Error!  Something went wrong" messages when I go from the Jira v8.0.2 dashboard to a specific project page.  If I go to project pages that have "*RapidBoard.jspa*" in the URL, I don't get any page at all.

In the /opt/atlassian/jira/logs/catalina.out log I see messages like:

31-Oct-2019 18:12:37.764 WARNING [http-nio-8080-exec-201] com.sun.jersey.spi.container.servlet.WebComponent.filterFormParameters A servlet request, to the URI https://jira-dev.guildmortgage.com/rest/activity-stream/1.0/preferences?_=1572545556111, contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.

In the /var/atlassian/application-data/jira/log/atlassian-jira.log log I see messages like:

2019-10-20 11:53:54,763 http-nio-8080-exec-64 INFO anonymous 713x258462x1 - 172.18.45.80 /status [c.a.j.authenticator.okta.OktaJiraAuthenticator30] Authentication result=URL_NOT_PROTECTED

In the /var/atlassian/application-data/jira/log/atlassian-jira-apdex.log log I see messages like:

2019-10-29 16:01:00,002 category: jira.header.menu.portfolio, apdex: {apdexScore=100, satisfiedCount=2, toleratingCount=0, frustratedCount=0}
2019-10-29 16:01:00,002 category: jira.dashboard, apdex: {apdexScore=25, satisfiedCount=0, toleratingCount=1, frustratedCount=1}

In the /var/atlassian/application-data/jira/log/atlassian-jira-security.log log I see messages like:

2019-10-31 18:19:11,484 http-nio-8080-exec-212 anonymous 1099x390287x2 - 34.225.120.58 /rest/webResources/1.0/resources HttpSession created [caouu0]
2019-10-31 18:19:11,486 http-nio-8080-exec-212 bmohler@guildmortgage.net 1099x390287x2 caouu0 34.225.120.58 /rest/webResources/1.0/resources HttpSession [caouu0] destroyed for 'bmohler@guildmortgage.net'

None of these seem immediately helpful.

How would you suggest that I troubleshoot these?

For the sake of providing a more complete picture, one of our administrators ran the following command in cd /opt/atlassian/jira and cd /var/atlassian thinking that this wouldn't break anything given that the jira/tomcat process was running under the jira account:

chown -R jira .

[Bruce Mohler]

Anyone?