[
https://issues.apache.org/jira/browse/TS-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692706#comment-13692706
]
ASF subversion and git services commented on TS-1946:
-----------------------------------------------------
Commit 783ce7204f5bb903b10877314f78f0d1b249fc4c in branch refs/heads/master
from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=783ce72 ]
TS-1946: reduce the verbosity of SSL handshake errors
Update SSL error logging routines so that we can log the SSL error
stack at debug level as well as error level. Update SSL error logging
to log the location of the caller, rather than the location of the
logging function.
Drop SSL server handshake logs to debug level so that they don't
overwhelm the diagnostics log. Handshake errors can be very common
and are not generally interesting.
> 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.6
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
