[
https://issues.apache.org/jira/browse/TS-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678259#comment-13678259
]
Leif Hedstrom commented on TS-1946:
-----------------------------------
Is it a legitimate error, that's worth logging? If so, it ought to go to
error.log, right? If not, I'd say just nuke it, or turn it into some more
verbose logging level such that normal operations don't see it. Filling
diags.log is bad mojo, since it's never rotated.
Btw, I don't know why it was marked for "Lua", I had set the components to
Logging and SSL. Sorry about that.
> 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: Leif Hedstrom
> 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 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
