[rabbitmq-discuss] timeout_waiting_for_tables on node that has not changed node name

[Simon MacMullen]

On 13/12/11 17:07, Elias Levy wrote:
> That is exactly correct.  The short hostnames could not be resolved, but
> RabbitMQ, Mnesia, and Erlang all failed to generate any sort of warning
> to that effect, resulting in a bit of a goose chase trying to figure out
> why a perfectly good node was failing to rejoin the cluster after a
> simple restart.

Yes. I've opened a bug for better diagnostics here.

Cheers, Simon

-- 
Simon MacMullen
RabbitMQ, VMware