My solution to this is to shut down the system rabbitmq instance altogether, since I only run rabbitmq instances as my user when running integration tests.
For this I added "chmod -x /usr/sbin/rabbitmq-multi" to /etc/rc.local, so it gets reset even after new rabbit packages are released.
My solution to this is to shut down the system rabbitmq instance altogether, since I only run rabbitmq instances as my user when running integration tests.
For this I added "chmod -x /usr/sbin/ rabbitmq- multi" to /etc/rc.local, so it gets reset even after new rabbit packages are released.