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

Ingela Andin ingela.andin@REDACTED
Wed Jul 11 18:48:37 CEST 2018


Hi Roger!

git branch

* (HEAD detached at OTP-21.0.2)


git blame -L 2742,2749 ssl_connection.erl

fbbf7a98975 (Ingela Anderton Andin 2017-08-31 18:31:06 +0200 2742)
log_alert(true, Role, ProtocolName, StateName, #alert{role = Role} = Alert)
->

fbbf7a98975 (Ingela Anderton Andin 2017-08-31 18:31:06 +0200 2743)     Txt
= ssl_alert:own_alert_txt(Alert),

fbbf7a98975 (Ingela Anderton Andin 2017-08-31 18:31:06 +0200 2744)
error_logger:info_report(io_lib:format("~s
~p: In state ~p ~s\n", [ProtocolName, Role, StateName, Txt]));

fbbf7a98975 (Ingela Anderton Andin 2017-08-31 18:31:06 +0200 2745)
log_alert(true, Role, ProtocolName, StateName, Alert) ->

6c8a0271f75 (Ingela Anderton Andin 2016-08-12 12:17:47 +0200 2746)     Txt
= ssl_alert:alert_txt(Alert),

fbbf7a98975 (Ingela Anderton Andin 2017-08-31 18:31:06 +0200 2747)
error_logger:info_report(io_lib:format("~s
~p: In state ~p ~s\n", [ProtocolName, Role, StateName, Txt]));

fbbf7a98975 (Ingela Anderton Andin 2017-08-31 18:31:06 +0200 2748)
log_alert(false, _, _, _, _) ->

6c8a0271f75 (Ingela Anderton Andin 2016-08-12 12:17:47 +0200 2749)     ok.

So this was not changed in the ssl application for OTP-21.

In the master branch, we have started to use logger and the plan is that
log_alert true will be same as setting log level notice that is the default
log level. We have also added a debug level and possibility to set the
level.


Maybe there is something unforeseen in logger or logger/lager interaction?


Regards Ingela Erlang/OTP team- Ericsson AB


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

> The report changed from 'error_logger:info_report' in OTP-20.x to
> 'error_logger:error_report' in OTP-21.x (and then to ?LOG_ERROR in
> master).
>
> This now results in a lot of noise in our error reporting, because we
> get "SSL: Socket error: etimedout #012" about 10 times a minute.
>
> Any chance this change could be reverted, please?
>
> Related: http://erlang.org/pipermail/erlang-questions/2016-
> December/091046.html
>
> Thanks,
> Roger.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180711/a7581e88/attachment.htm>


More information about the erlang-questions mailing list