[
https://issues.apache.org/jira/browse/TS-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754187#comment-15754187
]
Craig B commented on TS-5098:
-----------------------------
Good: e5090a83125046b7af0ad8c802b7408a431d9968 (7 October)
Good: 001b1e4b4a273ea24bcfa47792451510d858ae16 (18 October)
Good: 32d2ee6d338fdb3c8ff7fbbe00fa977382dbd111 (26 October)
Good: c2dd8840e3fb96e95ba0b693ed5ef9d73f688fa7 (27 October) TS-4993
Bad: c1ac5f8bf87fd4bc3a8e06507219970d83965acd (27 October) TS-4796
Bad: 0bd042856465420bb5ebe8db7412ba649988e891 (27 October) TS-4956
Bad: 102b66b9730780289ef71fa1ee33214cbcbcdde2 (16 December)
> Sig 11: Segmentation fault on TLS when destination server issues Reset
> ----------------------------------------------------------------------
>
> Key: TS-5098
> URL: https://issues.apache.org/jira/browse/TS-5098
> Project: Traffic Server
> Issue Type: Bug
> Components: TLS
> Reporter: Craig B
>
> On HEAD as of 16DEC2016 (102b66b9730780289ef71fa1ee33214cbcbcdde2)
> When in Forward proxy mode, connecting to an HTTPS site, where the
> destination site responds with TCP RESET, Traffic Server will restart due to
> Sig 11: Segmentation fault.
> If the upstream site instead silently drops the response, ATS will
> successfully proceed with 502 (Tunnel Connection Failed).
> No proxy chaining involved, direct: client -> ATS -> destination.
> Test machine: Debian Jessie (8.6) x86_64
> To replicate, make an HTTPS request - via ATS in forward-proxy-mode - to a
> local (non-firewalled) server, with nothing running on TCP/443.
> Watch manager.log for near immediate "[LocalManager::pollMgmtProcessServer]
> Server Process terminated due to Sig 11: Segmentation fault" followed by
> "[Alarms::signalAlarm] Server Process was reset"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
