nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Error 500

Digital Services_bafh0p

Hi All, recently we update for the lest version 08.0.2 from version 7.X.X.

After the update, the system request to restart, then, guess what? 500 ERROR!

This is the log's I have after this. Some good soul could help us?

Technical details
Log's referral number: 23ad38b6-1f42-4795-93ea-1768c1554e84

Cause
Referer URL: Unknown

******** UPDATE********

Thank you all the answers, but we decided to return the backup we did before starting the upgrade,

Now the upgrade was successful but Jira now is very slow.

Our JVM has 2Gb ram but still slow for only 5 users,,,

Accepted answers

Andy Heinzer

Hi,

I created this support case on your behalf. We would like to gather some logs from your system to better troubleshoot this issue.

https://getsupport.atlassian.com/servicedesk/customer/portal/20/GHS-152383

Regards,

Andy

Petter Gonçalves

Hello,

After investigating for similar errors and the scenario it was reproduced (After upgrade to JIRA 8.0), the most common root cause is that JIRA still referencing cached data in the old work directory.

It is important to make sure that when upgrading, JIRA is installed in a clean environment, although this is something we can easily miss.

That been said, please follow the steps below and check if it fixes the problem:

Stop JIRA
Delete the contents of the work directory
- JIRA standalone the work directory can be found in <install directory>/atlassian-jira-enterprise-4.1.2-standalone/work
- EAR/WAR the work directory will be unique to your specific applications server.
Restart JIRA.

JIRA will generate the contents of a new work directory upon startup. Make sure to set up a clean instance as outlined in Upgrading JIRA guide.

For more information about the steps provided, you can check the article below:

- Dashboard Fails to Display with Cannot Forward after Response has Been Committed Error

Let us know if this helps.

All comments

Andy Heinzer

Hi,

I created this support case on your behalf. We would like to gather some logs from your system to better troubleshoot this issue.

https://getsupport.atlassian.com/servicedesk/customer/portal/20/GHS-152383

Regards,

Andy

Petter Gonçalves

Hello,

After investigating for similar errors and the scenario it was reproduced (After upgrade to JIRA 8.0), the most common root cause is that JIRA still referencing cached data in the old work directory.

It is important to make sure that when upgrading, JIRA is installed in a clean environment, although this is something we can easily miss.

That been said, please follow the steps below and check if it fixes the problem:

Stop JIRA
Delete the contents of the work directory
- JIRA standalone the work directory can be found in <install directory>/atlassian-jira-enterprise-4.1.2-standalone/work
- EAR/WAR the work directory will be unique to your specific applications server.
Restart JIRA.

JIRA will generate the contents of a new work directory upon startup. Make sure to set up a clean instance as outlined in Upgrading JIRA guide.

For more information about the steps provided, you can check the article below:

- Dashboard Fails to Display with Cannot Forward after Response has Been Committed Error

Let us know if this helps.

Digital Services_bafh0p

Thank you for your help.

We did the snapshot before upgrading the server. So we return the Jira version for the version before the upgrade and upgrade the server. Works but very slow, the 500 error gone, but now every action takes more than 1 minute.

We are looking to understand why is so slow.

Digital Services_bafh0p

Hi Andrew, the version is the latest one.

Thank you

Petter Gonçalves

Thank you for the feedback!

We will be working on your issue in the ticket created by Andrew since performance issues need more details to be further investigated.

Digital Services_bafh0p

Hi Petterson,

I followed the suggestion to remove incompatible plugins and the speed returns to normal. Also, I'm reindexing to make sure I did all tentatives. The indexing still in progress. I will update soon the procedure done.

Thank you.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-service-desk

jira-server

jira-service-desk-server