[rabbitmq-discuss] gen_event handler rabbit_error_logger crashed. Reason badarg

[Matthias Radestock]

Bruno,

Bruno Thomas wrote:
> We have rabbitmq (1.8.0) in production since 7th of december. There is
> a virtual IP proxy in front of two rabbitmq server nodes (2 machines)
> clustered.
> 
> We see sometimes theses errors in rabbitmq logs, causing one node to
> fall, and then be restarted by the cluster :
> 
> =ERROR REPORT==== 22-Dec-2010::20:31:10 ===
> ** gen_event handler rabbit_error_logger crashed.
> ** Was installed in error_logger
> ** Last event was: {info_msg,<0.113.0>,
>                              {<0.161.0>,
>                               "closing TCP connection ~p from ~s:~p~n",
>                               [<0.19903.120>,"10.175.60.13",56518]}}
> ** When handler state == {resource,<<"/">>,exchange,<<"amq.rabbitmq.log">>}
> ** Reason == {badarg,[{ets,lookup,[rabbit_exchange_type_registry,topic]},
>                       {rabbit_exchange_type_registry,lookup_module,1},
>                       {rabbit_exchange,type_to_module,1},
>                       {rabbit_exchange,publish,3},
>                       {rabbit_basic,publish,1},
>                       {rabbit_error_logger,publish1,4},
>                       {rabbit_error_logger,handle_event,2},
>                       {gen_event,server_update,4}]}
> 
> Do you have an idea of what it means ?

That looks like a symptom of something quite fundamental having gone 
wrong, quite possibly some resource exhaustion, e.g. Erlang processes.

> Do you think we should upgrade to 2.2.0 ?

Yes!

Regards,

Matthias.