LogAnalyzer shows a some problems after Upgrade - should we care?

[TidoL]

Hi,

I hope someone can help us, we are in the middle of the upgrade downtime....

we just upgraded from Jira Server 8.5.1 to 8.13.8.

The Log Analyzer shows the messages below (the timestamps fit to the restarts of the application).

It hasn't shown these before, nor on our test environment as we tested the upgrade there.

So...

A) what's up? Something gone wrong with the MySQL-DB ist seems?

B) How bad is it? Can we allow hundreds of users to work on it on monday?

Help gladly appreciated,
Tido

Type	Urgency	Level	Problem	Last Occurrence	Matches
blue	Medium	ERROR	Cluster Cache Replication HealthCheck fails due to unable to complete within the timeout	42 minutes ago	12 matches, last match on line 135933
blue	Medium	WARN	JIRA Health Check Timeout	42 minutes ago	9 matches, last match on line 135931
blue	Medium	WARN	Troubleshoot long page load times in Jira server	44 minutes ago	90 matches, last match on line 135850
blue	Low	DEBUG	Find the last login date for a user in Jira server	44 minutes ago	9 matches, last match on line 135692
red	Low	ERROR	Add support for 4 byte characters in MySQL connection Fixed in 8.0.0	4 hours ago	134 matches, last match on line 123298
red	Low	ERROR	MySQL databases incapabable of handling 4-byte UTF-8 Characters. JIRA should handle this gracefully	4 hours ago	134 matches, last match on line 123298
blue	Medium	ERROR	Unable to proceed with Issue submission due to UNICODE chars and SQL code in text fields or description or attachment file name	4 hours ago	90 matches, last match on line 123298
blue	Medium	ERROR	Jira server throws SQL Exception while updating issues or importing data into MySQL due to encoding	4 hours ago	402 matches, last match on line 123298
blue	Medium	ERROR	UndeclaredThrowableException while Clicking Issues Navigation Menu in JIRA	4 hours ago	30 matches, last match on line 123233
blue	Medium	ERROR	Issue key increments unexpectedly on new issue creation in Jira server	4 hours ago	84 matches, last match on line 119437
red	Low	ERROR	Issue count increasing where by there's no issue created by mail handler due to database encoding	4 hours ago	28 matches, last match on line 119437
blue	Medium	ERROR	IMAP mail fails with FolderClosedException in logs in Jira server	4 hours ago	3 matches, last match on line 108950
blue	Medium	ERROR	java.net.SocketTimeoutException: Read timed while making a request to a remote server	4 hours ago	3 matches, last match on line 108928

[TidoL]

Hi Fadoua,

good questions, sorry not for providing the information right away:

We tested Jira quite thoroughly I would say (30 test cases, including open old issues, create, attachments witch weird characters, performance; we didn't test the number of specific issue types however).
Only issue: smilies from smartphones are not accepted any more (before, they were converted to a special kind of "?" character.
That was the direction the logs pointed as well with some of those lines.

The application started like normal, health check is all green.

Cheers,
Tido

[Tinker Fadoua]

@TidoL 

• What are you seeing in Jira logs?
• Did you test Jira?(Creating issues, create a test project, check if all issues are available, did you run some JQL queries before upgrade? You will need to run the same ones after upgrade to make sure that number of issues for specific Issue Types is still the same,....)
• Is application starting without issues?

Based on your answers I can have a better idea.

Best,

Fadoua