Failure deploying with event-bus-redis, BullMQ issue #9138
Labels
Comments
KareemAbbas1
changed the title
|
#9000 fixes this issue and the changes will be part of a release later today :) |
|
@olivermrbl Thanks a lot. I just have one question. I'm currently using version 1.20.6, which version should I update to in order for the new changes to take effect on my code? |
|
@KareemAbbas1, it will be available in the next release which is version 1.20.11. |
|
@olivermrbl Thank you for your help. |
You mean 1.20.10, right? |
Yes, you're right. Sorry about that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
Describe the bug
I'm trying to deploy my backend to Railway. I'm using event-bus-redis for production as mentioned in the docs. When I push for deployment, everything runs smoothly. The build is successful. When I check the deployment logs, everything is fine. I see that connection to Redis established, connection to event-bus-redis established, and connection to redis-cache established. However, I get an error saying "Error starting server". When I check the error stack details, I get a list of errors related to BullMQ attached below. I have followed the documentation while installing event-bus-redis and haven't changed anything. Everything is the default as defined below. The module is working fine on my local machine and I actually have some custom subscribers and working fine on my machine with no problems.
System information
Medusa version: 1.20.6
Event-bus-redis version: 1.8.13
Node.js version: 18.18.0
Database: Postgres
Operating system: Windows(in local development) In product I'm not quite sure, but I think Railway uses Docker and Linux.
Browser (if relevant): Not relevant.
Steps to reproduce the behavior
Expected behavior
Deploy successfully and be able to use event-bus-redis in production
If applicable, add screenshots to help explain your problem
Code snippets: the full list of the errors I have in my log related to BullMQ
Additional context
Before this error occurred I was facing the following error related to ioreds:
I solved it by appending "?family=0" to REDIS_URL and after that the connection was established successfully. Right after solving this error, I started seeing the errors related to BullMQ above.
The text was updated successfully, but these errors were encountered: