-
Bug
-
Resolution: Unresolved
-
High
-
None
-
7.4.0, 7.4.1, 7.4.2, 7.5.0, 7.5.1, 7.6.0, 7.13.0, 7.12.3
-
7.04
-
55
-
Severity 2 - Major
-
21
-
-
Summary
/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
Note that this bug is known to usually occur when the Database is configured with an unsupported collation
Environment
- JIRA 7.4.x (Server, Data Center)
Steps to Reproduce
- Startup a JDC node running JIRA 7.4.x
- Log in the node and ensure the node is running well (to avoid
)JRASERVER-59503 - Access the URL <node-address>/status
Expected Results
This will return the following JSON object
{"state":"RUNNING"}
Actual Results
This returns
{"state":"MAINTENANCE"}
and stays that way forever.
Manually performing a re-index doesn't help. Once the re-index completes, the state is still Maintenance.
Workaround and notes
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:
function clear_maintenance_mode_for_db_collation { maint_check=$( curl -s localhost:7101/status | grep -c "MAINTENANCE" | cat ) if [ "${maint_check}" -gt 0 ]; then collation_check=$( curl -s http://localhost:7101/secure/errors.jsp | grep -c "unsupported collation: utf8mb4_bin" | cat ) if [ "${collation_check}" -gt 0 ]; then curl -u "${JIRA_CREDS}" http://localhost:7101/secure/johnson/events/dismiss curl -u "${JIRA_CREDS}" http://localhost:7101/secure/johnson/warnings/acknowledge sleep 5s fi fi }
Please note we strongly advise an upgrade to Jira 8 or above which supports this natively
- is incorporated by
-
JRASERVER-59503 /status should return running and not starting when JDC node is already started up
- Closed
- relates to
-
JRASERVER-67135 JIRA Data Center node appear as Active when shutdown ungracefully
- Closed
-
JRASERVER-67138 /status url returns ERROR instead of MAINTENANCE during foreground reindexing
- Closed
-
JRASERVER-70382 /status returns 'Running' despite the instance being Johnsoned
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...