-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling Rabbit event_pusher handler causes crash #4446
Comments
Thank you for reporting this issue and providing information. We've added it to our backlog and will investigate the exchange creation process further. |
We couldn’t reproduce the issue on MongooseIM 6.2.1. The configuration looks correct and exchange creation worked without errors in our tests. |
Thanks for looking into it, I will try to provide a complete set-up to reproduce |
Hi @jacekwegr, I've created this minimal repository with a docker-compose setup to reproduce my issue: https://github.com/rthouvenin/mim-setup If you run Can you see what differs between this setup and your test? |
MongooseIM version: 6.2.1
Installed from: Docker
I would like to enable
mod_event_pusher
with a RabbitMQ handler, but when I do so MongooseIM crashes on startup with an error message saying that it could not create the RabbitMQ exchanges. I can't see any information on why the exchange creation fails.Here is the relevant config that I added:
(I also tried naming a single exchange and keeping the default for the others)
The connection to RabbitMQ works fine because if I removed the
mod_event_pusher
section and keep the outgoing pool, I can see in the logs that the connection is successful. The crash occurs only when enabling the event pusher module, while attempting to create the exchanges.The user has the permissions to create the exchange, as I am able to create them "manually" from the RabbitMQ admin interface. And creating the exchange beforehand does not solve the problem, MongooseIM still tries to create it (or at least crashes with the same error).
Anything I may have missed ?
The text was updated successfully, but these errors were encountered: