Consider that you have configured a running cluster with three nodes and one of your nodes suddenly fails. When you try to bring up that node using the following:
rabbitmq-server.bat
You get the dreadful BOOT FAILED
message along with an error description message of timeout_waiting_for_tables
and an Erlang stacktrace, as follows:
########## Starting broker... BOOT FAILED =========== Error description: {boot_step,database, {error, {timeout_waiting_for_tables, [rabbit_user,rabbit_user_permission,rabbit_vhost, rabbit_durable_route,rabbit_durable_exchange, rabbit_runtime_parameters,rabbit_durable_queue]}}} Log files (may contain more information): D:/software/RabbitMQ/rabbitmq_server-3.4.4/log/[email protected] D:/software/RabbitMQ/rabbitmq_server-3.4.4/log/[email protected] Stack trace: [{rabbit_table,wait,1,[]}, {rabbit_table,check_schema_integrity...