Error 503 after upgrading Jira

Yasmeen Kh May 23, 2021

Hello Dears,

I upgraded Jira recently to the latest version and got the following error after starting jira!


fe80:0:0:0:88c:faf0:4856:dbb7%13 810x24x1 - [23/May/2021:13:30:31 +0200] "GET /jira/- HTTP/1.1" 503 5 6 "-" "libcurl/7.54" "-"
fe80:0:0:0:88c:faf0:4856:dbb7%13 810x25x1 - [23/May/2021:13:30:34 +0200] "GET /jira/rest/capabilities- HTTP/1.1" 503 5 12 "-" "Bitbucket-7.11.2 (7011002)" "-"
127.0.0.1 810x26x1 - [23/May/2021:13:30:35 +0200] "GET /secure/johnson/data- HTTP/1.1" 503 5 11 "http://localhost:8080/secure/errors.jsp" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0" "-"
fe80:0:0:0:88c:faf0:4856:dbb7%13 810x27x1 - [23/May/2021:13:30:43 +0200] "GET /jira/rest/remote-event-consumer/1/capabilities- HTTP/1.1" 503 5 3 "-" "Bitbucket-7.11.2 (7011002)" "-"
127.0.0.1 810x28x1 - [23/May/2021:13:30:50 +0200] "GET /secure/johnson/data- HTTP/1.1" 503 5 12 "http://localhost:8080/secure/errors.jsp" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0" "-"
127.0.0.1 810x29x1 - [23/May/2021:13:30:52 +0200] "POST /jira/rest/usermanagement/1/search?entity-type=user&start-index=0&max-results=-1&expand=user HTTP/1.1" 503 5 4 "-" "Apache-HttpClient/4.5.13 (Java/1.8.0_241)" "-"
fe80:0:0:0:88c:faf0:4856:dbb7%13 811x30x1 - [23/May/2021:13:31:01 +0200] "GET /jira/- HTTP/1.1" 503 5 4 "-" "libcurl/7.54" "-"
127.0.0.1 811x31x1 - [23/May/2021:13:31:05 +0200] "GET /secure/johnson/data- HTTP/1.1" 503 5 7 "http://localhost:8080/secure/errors.jsp" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0" "-"
127.0.0.1 811x32x1 - [23/May/2021:13:31:20 +0200] "GET /secure/johnson/data- HTTP/1.1" 503 5 6 "http://localhost:8080/secure/errors.jsp" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0" "-"
127.0.0.1 811x33x1 - [23/May/2021:13:31:35 +0200] "GET /secure/johnson/data- HTTP/1.1" 503 5 6 "http://localhost:8080/secure/errors.jsp" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0" "-"
fe80:0:0:0:88c:faf0:4856:dbb7%13 811x34x1 - [23/May/2021:13:31:44 +0200] "GET /jira/rest/capabilities- HTTP/1.1" 503 5 3 "-" "Bitbucket-7.11.2 (7011002)" "-"
127.0.0.1 811x35x1 - [23/May/2021:13:31:50 +0200] "GET /secure/johnson/data- HTTP/1.1" 503 5 7 "http://localhost:8080/secure/errors.jsp" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0" "-"
127.0.0.1 812x36x1 - [23/May/2021:13:32:05 +0200] "GET /secure/johnson/data- HTTP/1.1" 503 5 5 "http://localhost:8080/secure/errors.jsp" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:88.0) Gecko/20100101 Firefox/88.0" "-"
fe80:0:0:0:88c:faf0:4856:dbb7%13 812x37x1 - [23/May/2021:13:32:13 +0200] "GET /jira/rest/remote-event-consumer/1/capabilities- HTTP/1.1" 503 5 4 "-" "Bitbucket-7.11.2 (7011002)" "-"

can you please help in this issue.

 

Thanks in advance,

Yasmeen

 

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 23, 2021

That's a log file telling you that when something is reaching Jira, it is responding with an error.

It would be useful to see what the actual error is - Jira goes to /secure/errors.jsp is a page that displays the underlying error to the end user.

Try visiting it in a browser (or just curl it from the command line and read the pile of html you get back - it won't be huge)

Yasmeen Kh May 23, 2021

could the issue be related to database? as i migrated it recently to postgres database ( it was sql database). Moreover, i noticed start-jira does not related to aatlassian jira service on the server, could we have an issue within the configuration files?

 

Kind Regards,

Yasmeen

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 23, 2021

It could be related to anything, database, networking, ssl, configuration file, an angry penguin chewing on cables.

There's no way to begin to say what this might be without reading the error, either from the screen it displays, or the application log file.

The service will indeed fail if the service is failing.

Yasmeen Kh May 23, 2021

Hello,

 

I checked the log file again and saw the following error :

 


2021-05-23 16:14:07,914+0200 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We couldn't start JIRA
2021-05-23 16:14:07,914+0200 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.
2021-05-23 16:14:07,914+0200 JIRA-Bootstrap INFO [c.a.jira.startup.DatabaseLauncher] Database transactions enabled: true
2021-05-23 16:14:07,916+0200 JIRA-Bootstrap INFO [c.a.jira.startup.DatabaseLauncher] Using JIRA's default for database transaction isolation level: 2
2021-05-23 16:14:07,998+0200 JIRA-Bootstrap WARN [c.a.jira.startup.DatabaseLauncher] JRADEV-23357: unable to select from the 'MovedIssueKey' entity.
2021-05-23 16:14:08,014+0200 JIRA-Bootstrap ERROR [c.a.jira.startup.LauncherContextListener] Unable to start JIRA.
java.lang.IllegalStateException: Need to rename the MOVED_ISSUE_KEY table, but there is existing data in it. Please contact Atlassian Support.
at com.atlassian.jira.startup.DatabaseLauncher.cleanupDatabaseTableName(DatabaseLauncher.java:246)
at com.atlassian.jira.startup.DatabaseLauncher.cleanupDatabaseTableNames(DatabaseLauncher.java:210)
at com.atlassian.jira.startup.DatabaseLauncher.start(DatabaseLauncher.java:73)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:139)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:307)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:202)
at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:135)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:102)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:100)
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
at java.lang.Thread.run(Thread.java:748)
2021-05-23 16:14:08,017+0200 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Startup is complete. Jira is ready to serve.
2021-05-23 16:14:08,021+0200 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 585 MiB. Committed: 897 MiB. Max: 2010 MiB
Non-heap memory : Used: 71 MiB. Committed: 87 MiB. Max: 1536 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 656 MiB. Committed: 984 MiB. Max: 3546 MiB
---------------------------------------------------------------------------------
2021-05-23 16:15:04,860+0200 http-nio-8080-exec-1 ERROR anonymous 975x1x1 - 192.168.90.41,fe80:0:0:0:88c:faf0:4856:dbb7%13 /jira/rest/capabilities [c.atlassian.instrumentation.Instrument] Unable to snapshot thread local operations (implementation of OpTimerFactory is not a ThreadLocalOpTimerFactory): null

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 23, 2021

Ok, that's pretty clear - there is a problem with the database.

Either the user connecting to it does not have the right permissions for access, or you've got corrupted data in it.

You said earlier you'd migrated from sql (which one?  Most databases are sql based) to postgresql.  How did you do that?

Suggest an answer

Log in or Sign up to answer