[
https://issues.apache.org/jira/browse/TS-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226924#comment-14226924
]
Sudheer Vinukonda commented on TS-1946:
---------------------------------------
[~sc0ttbeardsley] : The error logs have been changed to debug traces, but, a
bunch of counts have been added that can be queried through traffic_line. For
example, will the below work?
[sudheerv@dev1 net]$ sudo traffic_line -m . | grep ssl_error
proxy.process.ssl.ssl_error_want_write 0
proxy.process.ssl.ssl_error_want_read 50
proxy.process.ssl.ssl_error_want_x509_lookup 0
proxy.process.ssl.ssl_error_syscall 0
proxy.process.ssl.ssl_error_read_eos 0
proxy.process.ssl.ssl_error_zero_return 5
proxy.process.ssl.ssl_error_ssl 0
> Verbose SSL ERROR in diags.out
> ------------------------------
>
> Key: TS-1946
> URL: https://issues.apache.org/jira/browse/TS-1946
> Project: Traffic Server
> Issue Type: Bug
> Components: Logging, SSL
> Reporter: Leif Hedstrom
> Assignee: James Peach
> Labels: A
> Fix For: 3.3.5
>
>
> I'm seeing quite a few errors like below in diags.log (this site uses a self
> signed cert, not signed by a trusted CA):
> {code}
> [Jun 1 08:32:02.771] Server {0x420f4b90} ERROR: SSL_ServerHandShake
> [Jun 1 08:32:02.771] Server {0x420f4b90} ERROR: SSL::4:error:140760FC:SSL
> routines:SSL23_GET_CLIENT_HELLO:unknown protocol:s23_
> srvr.c:628:
> {code}
> I don't know (yet) what or why this error is generated, but I think we should
> either fix this, or move the error to error.log (which does get rotated
> properly). The main problem with putting this out on stderr/stdout and
> directed to diags.log is that diags.log never gets rotated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
