[rabbitmq-discuss] procedure for dealing with timeout_waiting_for_tables
tsuraan at gmail.com
Tue Sep 8 17:09:44 BST 2009
> Yes, the likely cause is your hostname change. If you recreate all the
> resources, stop rabbit, copy the saved persister logs back in, and
> start rabbit, it should do the trick.
I'm currently starting rabbit with the node name 'rabbit'. If I were
to always start it with 'rabbit at localhost' (or 'rabbit@<some other
constant name>', I guess), would I be guaranteed to not have this
problem, as long as the @name is something that maps to the local
machine? I assume that erlang implicitly uses rabbit@`hostname` when
the @ is left off, but I'm not entirely sure on that.
More information about the rabbitmq-discuss