Hello, as I was solving the connection between rabbitmq and OpenIAM AD connector. I mistakenly remove the rabbitmq container. Is there any way to restore it?
I tried creating new rabbitmq but esb, ui and more are all failing.
Thank you in advance for your support.
Hello @violettulips3270,
Thank you for reaching out! Yes, this has been encountered before and the recovery is straightforward. Please follow the steps below based on your installation type.
Important: This process may result in losing any pending messages in RabbitMQ queues, but your IAM data in the database will NOT be affected.
=======================================
IF YOU ARE ON A DOCKER INSTALLATION
=======================================
The recovery path depends on whether the RabbitMQ Docker volume still exists or was also lost.
FIRST: Check if the volume still exists —
docker volume ls | grep rabbitmq
[ CASE 1 ] Volume still exists (only the container was accidentally removed)
This is the simplest case. Just run:
./shutdown.sh
./startup.sh
The existing volume retains all vhost, user, and permissions data, so everything will come back automatically. No further steps are needed.
[ CASE 2 ] Volume is missing or corrupted
In this case, run the full setup again:
./shutdown.sh
./setup.sh
./startup.sh
The setup.sh script will recreate the RabbitMQ volume and re-initialize everything automatically — including all vhosts, users, and permissions. No manual rabbitmqctl commands are required.
Note: Since you were working on the AD connector connection when the container was removed, it is likely only the container was deleted and the volume may still be intact. We recommend checking Case 1 first before proceeding to Case 2.
=======================================
IF YOU ARE ON AN RPM INSTALLATION
=======================================
Please follow the official OpenIAM documentation for the RPM-based RabbitMQ re-initialization steps. The guide covers stopping the service, clearing the Mnesia directory, rejoining the cluster, and re-running the vhost/user initialization script:
RabbitMQ cluster went out of order
Please make sure to refer to the documentation version that matches your installed OpenIAM version.
=======================================
GOING FORWARD — PREVENTIVE TIPS
=======================================
- When troubleshooting connector connectivity issues (e.g. AD connector), avoid removing containers directly. Instead, check the logs first:
docker service logs openiam_rabbitmq
- To safely stop and restart all OpenIAM services at any time, always use:
./shutdown.sh
./startup.sh
Please let us know if you run into any issues during the recovery and we will be happy to assist.