Skip to content
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

Kombu==4.4.0 breaks celery / redis implementation Docker #1954

Closed
rich5851 opened this issue Mar 8, 2019 · 1 comment · Fixed by #1958
Closed

Kombu==4.4.0 breaks celery / redis implementation Docker #1954

rich5851 opened this issue Mar 8, 2019 · 1 comment · Fixed by #1958
Labels

Comments

@rich5851
Copy link

rich5851 commented Mar 8, 2019

What happened before?

Celery Workers started

What happens now?

kombu==4.4.0 released on the 3rd March 2019

Celery Workers fail to start with VersionMismatch
celeryworker_1 | kombu.exceptions.VersionMismatch: Redis transport requires redis-py versions 3.2.0 or later. You have 2.10.6

Updating to redis 3.2 not an option as it causes django_celery_beat that I am also using to no longer change the periodic tasks file when tasks are updated.

Last stable commit / Since when?

Steps to reproduce

Deployment local or production with docker
docker compose build and up

Fixed the issue by adding kombu==4.3.0 at bottom of requirements/base.txt

@rolep
Copy link
Contributor

rolep commented Mar 12, 2019

Then better to use kombu==4.4.0 cause 4.3.0 also has bug which I have encoutered: celery/kombu#1006
The bug is fixed in 4.4.0

Also am using django_celery_beat, but with database scheduler, seemingly with no such issues.

If using redis 2.x is preferred - then better stick with previous kombu version 4.2.xxx, but imho thats not in spirit of this project

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants