Jira Log scan error: We couldn't run the log analyzer

Nico n July 19, 2017

Hello,

I got a problem with Jira Support tool. When I try to access to the section Support tools -> Log analyzer, I get error: "We couldn't run the log analyzer"

Immediately, in Jira log I get the following:

2017-07-19 11:49:09,762 hercules INFO f844439d-dfa7-4795-8b2f-b475157c28a7 709x141x1 1xijher 170.251.204.174,127.0.0.1 /plugins/servlet/stp/view/hercules/execute [c.a.s.tools.hercules.LogScanTask] Scan failed:
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)
...

I didn't find any resolution about it. Could you help me ?

 

thanks

Nico

 

5 answers

0 votes
RichardW August 4, 2017

I am seeing this issue with Bamboo 6.0.3 as well:

2017-08-04 15:40:59,009 INFO [hercules] [LogScanTask] Scan failed: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure

0 votes
Nico n July 21, 2017

i don't think so, different exceptions

0 votes
MattS
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 20, 2017
0 votes
Nico n July 20, 2017

Thanks! Certificate is valid. I have tested with SSLpoke from the unix machine where Jira is installed, and the result is: Successfully connected

This test should simulate Jira connecting it self.

Beside, I have tested SSLpoke to confluence.atlassian.com, necessary to download regular expression pattern files (as suggested in https://confluence.atlassian.com/support/log-scanner-and-scheduled-log-scanner-790796841.html). Even with curl is OK.

Any other ideas ?

Thanks

Nico

0 votes
MattS
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 19, 2017

Looks like some problem with JIRA connecting to itself using SSL? Check your certificate is valid, and you can use sslpoke to test this as well.

Suggest an answer

Log in or Sign up to answer