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

[Simon MacMullen]

On 23/05/12 16:24, Glade Diviney wrote:
> 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:

<snip>

> ** 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?

Aha!

That function was renamed in 2.8.2. Are you by any chance running a 
cluster with mixed RabbitMQ versions?

That is very likely to lead to random breakage - like this.

Future versions of RabbitMQ will probably refuse to start instead.

Cheers, Simon

-- 
Simon MacMullen
RabbitMQ, VMware