-
Notifications
You must be signed in to change notification settings - Fork 0
Recurrent error
This error occurs when the system attempts to run RabbitMQ but detects two conflicting versions of the Erlang Runtime System (ERTS) active simultaneously (e.g., conflicting versions 14.2.5.12 and 16.2).
This usually happens after a failed upgrade or if a newer, experimental version of Erlang (like OTP 28) was installed alongside a stable version. The conflict causes the RabbitMQ node to fail at startup and locks the installation directories, preventing standard deletion.
To resolve this, you must perform a "Clean Install" by forcing all processes to stop, isolating the corrupted files, and reinstalling a known compatible pair.
Standard uninstallation often fails because epmd.exe (Erlang Port Mapper Daemon) remains running in the background, locking the files.
Open PowerShell as Administrator and run the following to kill the locks:
# Force kill the Port Mapper, Erlang Runtime, and Service wrapper
taskkill /F /IM epmd.exe
taskkill /F /IM erl.exe
taskkill /F /IM erlsrv.exe
Before uninstalling, rename the existing directories. This ensures that even if the uninstaller fails to remove some files, the new installation won't accidentally use the corrupted configuration or locked files.
- Navigate to
C:\Program Files\(or your custom install path). - Find the erl (Erlang) folder(s) and rename them to:
..._BROKEN
Go to Control Panel > Programs and Features or go in the folder and select launch uninstall.exe:
- Uninstall ALL listed versions of Erlang OTP (ensure both the old and new versions are removed).
- Uninstall RabbitMQ Server.
Install the software in the following order. Do not use bleeding-edge versions (like Erlang 28) for production RabbitMQ instances.
-
Step A: Install Erlang (Stable)
-
Version: OTP 26.2.5.5
-
Action: Install this first.
-
Step B: Install RabbitMQ
-
Version: 4.2.2 (or latest stable 4.x)
-
Action: Install this second.