-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.12.1, 8.20.0
-
None
-
8.12
-
1
-
Severity 3 - Minor
-
Issue Summary
As part of JRASERVER-61595, a new message was introduced sharing to the user that Jira that plugins are initialised and that Jira is actually ready to serve traffic:
Startup is complete. Jira is ready to serve
However this message shows in even scenarios where Jira's startup is faulted and therefore is not ready to serve traffic
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Configure Jira 8.20.0 to connect to a Postgres 9.4 database with a user that just has connect privileges, no more
Expected Results
The startup should fail, and no "ready to serve" message should be logged
Actual Results
The Jira application log shows "ready to serve" :
2022-12-28 18:55:06,119+1100 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We couldn't start JIRA 2022-12-28 18:55:06,119+1100 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] An error occurred while trying to start JIRA. We can't give you any more detail right now, we suggest checking the logs for more detail and contacting our support team. See our documentation for more information on contacting our support team and creating a support zip. <SNIP> 2022-12-28 18:55:06,184+1100 JIRA-Bootstrap ERROR [c.a.jira.startup.LauncherContextListener] Unable to start JIRA. com.atlassian.jira.exception.DataAccessException: org.postgresql.util.PSQLException: ERROR: permission denied for relation moved_issue_key at com.atlassian.jira.startup.DatabaseLauncher.cleanupDatabaseTableName(DatabaseLauncher.java:254) at com.atlassian.jira.startup.DatabaseLauncher.cleanupDatabaseTableNames(DatabaseLauncher.java:210) at com.atlassian.jira.startup.DatabaseLauncher.start(DatabaseLauncher.java:73) <SNIP> at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154) at java.base/java.lang.Thread.run(Thread.java:829) Caused by: org.postgresql.util.PSQLException: ERROR: permission denied for relation moved_issue_key <SNIP> 2022-12-28 18:55:06,187+1100 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve.
/status endpoint return non-success status:
curl -sS -w "%{http_code}\n" http://localhost:48200/j8200/status 503
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is caused by
-
JRASERVER-61595 JIRA start-up message is misleading - You can now access JIRA through your web browser.
- Closed