Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

can not create jira issue

arno
Contributor
November 2, 2024

Hi all

    Due to the limitations of the server, we will carry out the migration of jira in the near future. According to the guidance of the official document, we have installed the new jira service in the new server, replaced the main directory data, and updated the relevant configuration files

    Our service and database are deployed separately, backed up daily with the mysqldump command, and we restore to a new database with the backup sql file and assign the new database to the new server. The jira service started normally, but we were unable to create an issue

When we create an issue or query with a jql statement, an error message is displayed

1.png

And the left column of the project is empty

2.png

 

We have performed the refactoring of the index operation, but this does not solve the problem, what is the cause of the problem

1 answer

1 accepted

1 vote
Answer accepted
Robert Wen_Cprime_
Community Champion
November 2, 2024

Hi @arno .  What shows up in the log files (atlassian-jira.log)?

arno
Contributor
November 2, 2024

你好 @Robert Wen_Cprime_ 

   感谢你的回复

  当我创建问题时,日志显示如下

4.png

Robert Wen_Cprime_
Community Champion
November 2, 2024

Here's what I found for problems with XSRF errors.  You may have to contact Atlassian Support about this problem.

https://community.atlassian.com/t5/Jira-questions/XSRF-check-failed/qaq-p/999637

This Community post references this KB https://confluence.atlassian.com/jirakb/creating-project-throws-error-creating-project-xsrf-check-failed-397083076.html

 

YY Brother
Community Champion
November 2, 2024

It seems jira server is not supported by Atlassian anymore @Robert Wen_Cprime_ 

Robert Wen_Cprime_
Community Champion
November 2, 2024

True, support for Jira Server ended in February.  so contacting Atlassian Support is not an option.

arno
Contributor
November 3, 2024

Hi @Robert Wen_Cprime_ 

thank you for your help

I have found the cause of this problem, which is caused by our different tomcat configurations. I modified the server.xml file, and it is now back to normal, but we have encountered other problems, and this problem will be closed

Like # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.13.3
TAGS
AUG Leaders

Atlassian Community Events