Erlang client error logging

61 views
Skip to first unread message

Tõnis Kasekamp

unread,
Jul 14, 2017, 5:05:13 AM7/14/17
to rabbitmq-users
When the RabbitMQ server is unavailable, the erlang-client logs that error in the following format. The supervisor report includes the RabbitMQ username and password, in this case "guest". How to remove them from the error log? 

=CRASH REPORT==== 14-Jul-2017::08:41:42 ===
  crasher
:
    initial call
: amqp_gen_connection:init/1
    pid
: <0.1945.0>
    registered_name
: []
    exception
exit: socket_closed_unexpectedly
     
in function  gen_server:terminate/7 (gen_server.erl, line 812)
    ancestors
: [<0.1934.0>,amqp_sup,<0.1822.0>]
    messages
: []
    links
: [<0.1934.0>,#Port<0.3834>]
    dictionary
: [{process_name,
                     
{amqp_gen_connection,
                         
<<"client 172.17.0.8:60577 -> 10.0.2.2:5672">>}}]
    trap_exit
: true
    status
: running
    heap_size
: 1598
    stack_size
: 27
    reductions
: 1708
  neighbours
:


=SUPERVISOR REPORT==== 14-Jul-2017::08:41:42 ===
     
Supervisor: {<0.1934.0>,amqp_connection_sup}
     
Context:    child_terminated
     
Reason:     socket_closed_unexpectedly
     
Offender:   [{pid,<0.1945.0>},
                 
{name,connection},
                 
{mfargs,
                     
{amqp_gen_connection,start_link,
                         
[<0.1937.0>,
                           
{amqp_params_network,<<"guest">>,<<"guest">>,
                               
<<"/">>,"10.0.2.2",5672,0,0,0,5000,none,
                               
[#Fun<amqp_auth_mechanisms.plain.3>,
                               
#Fun<amqp_auth_mechanisms.amqplain.3>],
                               
[],[]}]}},
                 
{restart_type,intrinsic},
                 
{shutdown,brutal_kill},
                 
{child_type,worker}]


=SUPERVISOR REPORT==== 14-Jul-2017::08:41:42 ===
     
Supervisor: {<0.1934.0>,amqp_connection_sup}
     
Context:    shutdown
     
Reason:     reached_max_restart_intensity
     
Offender:   [{pid,<0.1945.0>},
                 
{name,connection},
                 
{mfargs,
                     
{amqp_gen_connection,start_link,
                         
[<0.1937.0>,
                           
{amqp_params_network,<<"guest">>,<<"guest">>,
                               
<<"/">>,"10.0.2.2",5672,0,0,0,5000,none,
                               
[#Fun<amqp_auth_mechanisms.plain.3>,
                               
#Fun<amqp_auth_mechanisms.amqplain.3>],
                               
[],[]}]}},
                 
{restart_type,intrinsic},
                 
{shutdown,brutal_kill},
                 
{child_type,worker}]

Michael Klishin

unread,
Jul 14, 2017, 6:11:47 AM7/14/17
to rabbitm...@googlegroups.com
This is not something that RabbitMQ Erlang client logs but rather parts of Erlang/OTP.

I can think of 2 ways:

 * Disable all crash report logging (I don't think it's a good idea)
 * Use x509 certificates for authentication (see https://github.com/rabbitmq/rabbitmq-auth-mechanism-ssl)

All other options include client library modifications (that would avoid crashes for
certain types of issues).
 

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ

Tõnis Kasekamp

unread,
Jul 14, 2017, 7:39:57 AM7/14/17
to rabbitmq-users
Thank you.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages