[rabbitmq-discuss] Clustered server doesn't permit local connections

Glade Diviney gladed at gmail.com
Wed May 23 16:24:24 BST 2012


Hi Simon,

Your instinct may be right on alarms. I did service rabbitmq stop, cleared
the logs, the service rabbitmq start and saw this in rabbit.log:

=INFO REPORT==== 23-May-2012::15:20:15 ===
Limiting to approx 924 file handles (829 sockets)

=INFO REPORT==== 23-May-2012::15:20:15 ===
Memory limit set to 1503MB of 3758MB total.

=INFO REPORT==== 23-May-2012::15:20:15 ===
Disk free limit set to 3758MB

=INFO REPORT==== 23-May-2012::15:20:15 ===
Disk free space limit now exceeded. Free bytes:3678556160 Limit:3941388288

=INFO REPORT==== 23-May-2012::15:20:15 ===
    alarm_handler: {set,{{resource_limit,disk,'rabbit at ip-10-70-82-246'},[]}}

=INFO REPORT==== 23-May-2012::15:20:15 ===
msg_store_transient: using rabbit_msg_store_ets_index to provide index

=INFO REPORT==== 23-May-2012::15:20:15 ===
msg_store_persistent: using rabbit_msg_store_ets_index to provide index

=INFO REPORT==== 23-May-2012::15:20:15 ===
started TCP Listener on [::]:5672

=INFO REPORT==== 23-May-2012::15:20:15 ===
rabbit on node 'rabbit at ip-10-12-183-2' up

=ERROR REPORT==== 23-May-2012::15:20:15 ===
** gen_event handler rabbit_alarm crashed.
** Was installed in alarm_handler
** Last event was: {register,<2894.58.0>,
                             {rabbit_alarm,remote_conserve_resources,[]}}
** When handler state == {alarms,
                             {dict,0,16,16,8,80,48,
                                 {[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                  [],[]},

 {{[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                   [],[]}}},
                             {dict,1,16,16,8,80,48,
                                 {[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                  [],[]},
                                 {{[],[],[],[],[],[],
                                   [['rabbit at ip-10-70-82-246',disk]],
                                   [],[],[],[],[],[],[],[],[]}}}}
** Reason == {'function not exported',

 [{rabbit_alarm,remote_conserve_resources,[<2894.58.0>,true]},
                  {rabbit_alarm,internal_register,3},
                  {rabbit_alarm,handle_event,2},
                  {gen_event,server_update,4},
                  {gen_event,server_notify,4},
                  {gen_event,handle_msg,5},
                  {proc_lib,init_p_do_apply,3}]}

What's the prognosis, doc?

Thanks,
-Glade

On Wed, May 23, 2012 at 3:35 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> On 23/05/12 11:22, Simon MacMullen wrote:
>
>> On 23/05/12 00:38, Glade wrote:
>>
>>> {error,{badarg,{error,bad_**module}},
>>> 'connection.open',
>>>
>>
>> Hmm. This looks like the Erlang VM is failing to load one of RabbitMQ's
>> modules. This should really not happen.
>>
>
> Gah, no this isn't true at all. It's breaking trying to register with the
> alarm handler. Could you post the main and sasl logs somewhere?
>
>
> Cheers, Simon
> --
> Simon MacMullen
> RabbitMQ, VMware
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120523/15053546/attachment.htm>


More information about the rabbitmq-discuss mailing list