Ten thousand lines of logging when starting TLS connection

Since upgrading to OTP-25, whenever a TLS connection is started, this causes an extreme amount of logging:

=PROGRESS REPORT==== 24-Jan-2023::10:29:24.145614 ===                                                                                                                                                                                                                                                                                                                                                                                       
    supervisor: {<0.849.0>,tls_dyn_connection_sup}                                                                                                                                                                                                                                                                                                                                                                                          
    started: [{pid,<0.852.0>},                                                                             
              {id,receiver},                                                                               
              {mfargs,                                                                                     
                  {ssl_gen_statem,start_link,                                                              
                      [client,<0.851.0>,"host.name.com",443,                                        
                       #Port<0.69>,                                                                        
                       {#{alpn_preferred_protocols => undefined,                                           
                          sni_hosts => [],early_data => undefined,                                         
                          hibernate_after => infinity,                                                     
                          ciphers =>                                                                       
                              [<<19,2>>,                          
                          ..... more than 10.000 lines removed ...
                           {socket_options,binary,raw,0,0,false},                                             
                        undefined},                                                                        
                       <0.789.0>,                                                                          
                       {gen_tcp,tcp,tcp_closed,tcp_error,tcp_passive}]}},                                  
              {restart_type,temporary},                                                                    
              {significant,true},                                                                          
              {shutdown,5000},                                                                             
              {child_type,worker}]  

The majority of the 10000 (!) lines of logging is caused by a dump of the cacerts. This makes debugging very difficult, since it completely overflows the terminal.

Has anyone else seen this, and is there a solution?

1 Like

I guess the easiest way to get rid of them is to not use SASL logs. Perhaps we can mitigate this in the future. Personally, I think all progress reports in SASL ought to be debug-level logging but this is legacy that is hard to change.

1 Like