7.4.0, 7.4.1, 7.4.2, 7.5.0, 7.5.1, 7.6.0, 7.13.0, 7.12.3
Severity 2 - Major
Atlassian Update – 30 May 2023 Dear Customers, Thank you for taking the time to file and comment on this issue. We realize it still occurs and impacts your organization. We are now working on multiple customer requests and on new features, so we have to postpone our resolution of this issue. We’ve decided to move this issue to our long-term backlog. Please continue watching this ticket for future updates and changes in the timeline that impacts your work. Best regards Daria Misiowiec Software Engineer, Jira DC
/status request to JIRA Data Center returns "MAINTENANCE" instead of "RUNNING" when the node is actually Running and not in Maintenance mode.
This affects JIRA Server as well.
Note that this bug is known to usually occur when the Database is configured with an unsupported collation
- JIRA 7.4.x (Server, Data Center)
- Startup a JDC node running JIRA 7.4.x
- Log in the node and ensure the node is running well (to avoid
- Access the URL <node-address>/status
This will return the following JSON object
and stays that way forever.
Manually performing a re-index doesn't help. Once the re-index completes, the state is still Maintenance.
Please check Jira does not contain any startup warnings. This can be done by accessing
<Jira BASE URL>/secure/errors.jsp
Quite common case the issue occurs when Jira's database is using an unsupported collation. See an example below.
If that is the case, you can follow the instructions to fix that on your instance https://confluence.atlassian.com/jirakb/health-check-database-collation-790955315.html
If you decide to utilize MySQL's utf8mb4_bin collation in Jira versions 7.6 or 7.13 the following automation script can be used to acknowledge the database collation warning:
Please note we strongly advise an upgrade to Jira 8 or above which supports this natively