[
https://issues.apache.org/jira/browse/DISPATCH-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617739#comment-16617739
]
Carsten Lohmann commented on DISPATCH-1086:
-------------------------------------------
We also got this issue.
Using the additional log information provided by PROTON-1886 (with PN_TRACE_DRV
set to 1), there was this log output:
{noformat}
[0x7feae80d4f30]:Client SSL socket created.
[0x7feaf0142120]:Client SSL socket created.
[0x7feae80d4f30]:Read 26 bytes from SSL socket for app
[0x7feae80d4f30]:SSL socket freed.
[0x7feaf0142120]:Read 26 bytes from SSL socket for app
[0x7feaf0142120]:SSL socket freed.
[0x7feaec0c4e60]:SSL socket setup failure.
[0x7feaec0c4e60]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
2018-09-17 15:48:49.713040 +0000 AUTHSERVICE (warning) Cannot initialise SSL
[0x7feaec0c4e60]:SSL socket setup failure.
[0x7feaec0c4e60]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
[0x7feae805ea00]:SSL socket setup failure.
[0x7feae805ea00]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
2018-09-17 15:48:49.713156 +0000 AUTHSERVICE (warning) Cannot initialise SSL
[0x7feae805ea00]:SSL socket setup failure.
[0x7feae805ea00]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
[0x7feae8116100]:SSL socket setup failure.
[0x7feae8116100]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
2018-09-17 15:48:49.758598 +0000 AUTHSERVICE (warning) Cannot initialise SSL
[0x7feae8116100]:SSL socket setup failure.
[0x7feae8116100]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
[0x7feae806adf0]:SSL socket setup failure.
[0x7feae806adf0]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version
2018-09-17 15:48:49.762368 +0000 AUTHSERVICE (warning) Cannot initialise SSL
[0x7feae806adf0]:SSL socket setup failure.
[0x7feae806adf0]:error:140BA0E4:SSL routines:SSL_new:ssl ctx has no default ssl
version{noformat}
After the last line above, the router exited with a seg fault.
> Dispatch Router sporadically goes into a state where TLS connections to the
> auth service fail
> ---------------------------------------------------------------------------------------------
>
> Key: DISPATCH-1086
> URL: https://issues.apache.org/jira/browse/DISPATCH-1086
> Project: Qpid Dispatch
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: Keith Wall
> Priority: Major
>
> Whilst running performance tests against Enmasse, we periodically see a
> problem where Dispatch Router (1.1.0) goes into a state where fails to form
> TLS connections to the authservice. When this occurs, the router needs to be
> restarted to restore service. There does not seem to be a pattern to when the
> issue occurs, but in all cases where it has been seen, the test case included
> tens or hundreds of concurrently formed connections.
> The following message is written to the log:
>
> {noformat}
> 2018-07-06 10:38:45.543519 +0000 AUTHSERVICE (warning) Cannot initialise
> SSL{noformat}
> Unfortunately turning up the router logging (using the following command)
> reveal no more useful information. This Proton improvement JIRA was raised to
> include the diagnostics from OpenSSL.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
