[erlang-questions] Logging level of "SSL: Socket error"

[Ingela Andin]

Hi Roger!

I see, those error loggings are not affected by the log_alert option as
they are distribution logs and not TLS alert protocol logs. I agree the
change might be accidental. We will have to review this.

Regards Ingela Erlang/OTP team - Ericsson AB

2018-07-11 19:31 GMT+02:00 Roger Lipscombe <roger@REDACTED>:

> Hi Ingela,
>
> On 11 July 2018 at 18:27, Roger Lipscombe <roger@REDACTED> wrote:
> > https://github.com/erlang/otp/blob/OTP-21.0/lib/ssl/src/ssl_
> connection.erl#L1341-L1342
> >
> >     Report = io_lib:format("SSL: Socket error: ~p ~n", [Reason]),
> >     error_logger:error_report(Report),
> >
>
> (pressed send too quickly...)
>
> vs.
>
> https://github.com/erlang/otp/blob/OTP-20.3.2/lib/ssl/src/
> ssl_connection.erl#L1117-L1118
>
>     Report = io_lib:format("SSL: Socket error: ~p ~n", [Reason]),
>     error_logger:info_report(Report),
>
> It changed in https://github.com/erlang/otp/commit/
> 6e28a7909c665cc316d657dda02a2b8655ecc5da,
> but it's unclear whether it was deliberate or not.
>
> Thanks,
> Roger.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180711/04ac92f0/attachment.htm>