Waiting for Mnesia tables timeout during RabbitMQ cluster node startup

Question

Diagnosing Mnesia sync failure when log location and rotation vary by deployment
A RabbitMQ node refuses to boot, emitting repeated Waiting for Mnesia tables messages followed by a timeout. The first ERROR line after Starting RabbitMQ typically identifies the failing subsystem, but the log file path, rotation policy, and retention defaults differ across package installs (/var/log/rabbitmq
Constraints and uncertainty

Built-in rotation is controlled by log.file.rotation settings in rabbitmq.conf, yet defaults change between versions and packaging formats.
External log shippers (e.g., Fluentd, Vector) may be required in containerized environments, but the decision to rely on built-in rotation versus external collection remains unresolved for many operators.
Crash dumps (erl_crash.dump) are written separately and may be the only artifact when the node dies without a clear broker ERROR line.

Specific questions

How does the effective log directory and rotation behavior differ between package, Docker, and Kubernetes deployments for a given RabbitMQ version?
Which log.file.rotation settings guarantee that the Mnesia sync timeout ERROR lines are retained long enough for post-mortem analysis?
Should operators rely on built-in rotation or deploy external log shippers to ensure startup failure logs are preserved?

Waiting for Mnesia tables timeout during RabbitMQ cluster node startup

Diagnosing Mnesia sync failure when log location and rotation vary by deployment

`Constraints and uncertainty`

Specific questions

0 answers

Your perspective belongs here.

0 question comments