[rabbitmq-discuss] procedure for dealing with timeout_waiting_for_tables

tsuraan tsuraan at gmail.com
Mon Sep 7 19:08:03 BST 2009

I had a machine that had the timeout_waiting_for_tables (not in a
cluster, just a single node).  I'm guessing that its hostname had
changed, and that was making mnesia angry.  I have two questions about
this.  Is there a good way to figure out exactly why mnesia isn't
starting, i.e. is it a hostname change, a corrupt mnesia file, etc?

Second, to fix this, I thought I could copy out my persister logs,
wipe the rabbit dir from /var/lib/.../mnesia, restart rabbit, and move
the persisters back in.  That didn't seem to work, since the queues
weren't defined anymore, so the log replay apparently just threw
everything away.  Would remaking my exchanges, bindings, and queues,
then moving in my persister logs do the trick?

The full error from the log was:

=INFO REPORT==== 8-Sep-2009::02:53:25 ===
    application: rabbit
    exited: {{timeout_waiting_for_tables,
    type: temporary

=INFO REPORT==== 8-Sep-2009::02:53:25 ===
    application: mnesia
    exited: stopped
    type: temporary

=INFO REPORT==== 8-Sep-2009::02:53:25 ===
    application: os_mon
    exited: stopped
    type: temporary

That looks pretty standard from what I could find on this list, and it
seems to be related to hostname changes, but I couldn't see how to fix
it from there.

More information about the rabbitmq-discuss mailing list