# How to resolve the RabbitMQ error log displaying "Error while waiting for Mnesia tables: {timeout\_waiting\_for\_tables, \[rabbit\_user, rabbit\_user\_permission, ...\]}"?

**URL:** <https://forum.wise-paas.advantech.com/t/how-to-resolve-the-rabbitmq-error-log-displaying-error-while-waiting-for-mnesia-tables-timeout-waiting-for-tables-rabbit-user-rabbit-user-permission/1728>\
**Category:** Platform Operation & Maintenance\
**Tags:** EnSaaSRabbitMQ\
**Created:** [August 5, 2026, 9:21am UTC](https://forum.wise-paas.advantech.com/t/how-to-resolve-the-rabbitmq-error-log-displaying-error-while-waiting-for-mnesia-tables-timeout-waiting-for-tables-rabbit-user-rabbit-user-permission/1728 "2026-08-05T09:21:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sk.chen](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@sk.chen](https://forum.wise-paas.advantech.com/u/sk.chen)\
**Post date:** [August 5, 2026, 9:21am UTC](https://forum.wise-paas.advantech.com/t/how-to-resolve-the-rabbitmq-error-log-displaying-error-while-waiting-for-mnesia-tables-timeout-waiting-for-tables-rabbit-user-rabbit-user-permission/1728/1 "2026-08-05T09:21:39Z")

</div>

RabbitMQ is HA architecture

 ![image](https://canada1.discourse-cdn.com/flex032/uploads/wisepaasforum/original/1X/a0c7d2a662cb8fafc2d0fb53c48df84bef0f81b0.jpeg)

Rabbitmq log

 ![image](https://canada1.discourse-cdn.com/flex032/uploads/wisepaasforum/original/1X/a4dd3c041da3146d244ec3ecde596564fbebb4f0.jpeg)

---

<div class="post-metadata">

**Author:** ![sk.chen](https://avatars.discourse-cdn.com/v4/letter/s/6f9a4e/32.png) [@sk.chen](https://forum.wise-paas.advantech.com/u/sk.chen)\
**Post date:** [August 5, 2026, 9:35am UTC](https://forum.wise-paas.advantech.com/t/how-to-resolve-the-rabbitmq-error-log-displaying-error-while-waiting-for-mnesia-tables-timeout-waiting-for-tables-rabbit-user-rabbit-user-permission/1728/2 "2026-08-05T09:35:45Z")

</div>

RabbitMQ internally uses the Mnesia database to synchronize cluster state. When all nodes in an HA cluster have been shut down, RabbitMQ stipulates that “the last node shut down must be the first to start.”

Therefore, in your current situation: the Pod does not believe it is the last node to be shut down, hence the error. The solution is as follows.

1. Shutting down RabbitMQ using the `scale` command:

2. Deleting the RabbitMQ PVC (the HA architecture will have 3 PVCs):

3. Restarting RabbitMQ using the `scale` command: