Jira stopped after plugins update

[Ivan]

Hi,

My jira is version: 8.8.0

Jira crashed after updating packages.

In browser: refused to connect

I tried a few things, but without success:

https://community.atlassian.com/t5/Jira-questions/JIRA-failed-to-update-add-ons/qaq-p/442296

https://confluence.atlassian.com/jirakb/jira-startup-fails-with-message-that-required-plugins-are-not-started-254738702.html

https://community.atlassian.com/t5/Jira-questions/Jira-doesn-t-startup/qaq-p/1201445

https://confluence.atlassian.com/jirakb/re-index-in-jira-fails-due-to-indexformattoooldexception-973482953.html

Attached log: https://gist.github.com/ivanelson/d6dea001e94a430062efb8ea9038ad3d

I just found this:

2020-09-21 15:30:13,458-0300 HealthCheck:thread-3 DEBUG ServiceRunner     [o.s.b.factory.support.DefaultListableBeanFactory] Finishe
d creating instance of bean 'com.atlassian.troubleshooting.jira.healthcheck.support.StorageIndexSnapshotHealthCheck'
2020-09-21 15:30:13,458-0300 HealthCheck:thread-4 ERROR ServiceRunner     [c.a.t.j.healthcheck.support.GadgetFeedUrlHealthCheck] An
error occurred when performing the Gadget feed URL healthcheck
org.apache.http.conn.HttpHostConnectException: Connect to sistemas.claudinosa.com.br:443 [sistemas.claudinosa.com.br/172.16.2.228] f
ailed: Connection refused (Connection refused)
       at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:156)
       at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:374)
       at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393)
       at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
       at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
       at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
       at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
       at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
       at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
       at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108)
       at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
       at com.atlassian.troubleshooting.jira.healthcheck.support.GadgetFeedUrlHealthCheck.check(GadgetFeedUrlHealthCheck.java:56)
       at com.atlassian.troubleshooting.healthcheck.impl.PluginSuppliedSupportHealthCheck.check(PluginSuppliedSupportHealthCheck.ja
va:49)
       at java.util.concurrent.FutureTask.run(FutureTask.java:266)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
       at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
       at java.net.PlainSocketImpl.socketConnect(Native Method)
       at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
       at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
       at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
       at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
       at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:368)
       at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142)
       ... 16 more
2020-09-21 15:30:13,458-0300 HealthCheck:thread-2 DEBUG ServiceRunner     [o.s.b.factory.support.DefaultListableBeanFactory] Creatin
g instance of bean 'com.atlassian.troubleshooting.jira.healthcheck.support.GadgetFeedUrlHealthCheck'

Best regards

[Daniel Ebers]

Hi Ivan,

welcome to the Atlassian Community!

From the logs you provided (as well as them on github) there is no apparent reason for a application that would not load - at least not on first sight.

There are some error about a refused connection but at this time only for the gadget feed URL healthcheck. It might be that this also applies to other parts (for example to the application as such) but this is not recognizable at this state from reading the logs.

Best guess is to further crawl through the logs for some ERROR/SEVERE messages and/or consult a system administrator to double check.

There were cases where a restart of a server (if it took place on your end at all) let firewall rules to become active again what can lead to the assumption that the application is down where it is actually just behind a firewall then.

Cheers,
Daniel