-
-
Notifications
You must be signed in to change notification settings - Fork 930
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
"Error 32 while writing to socket. Broken pipe" After upgrading to kombu 4.4.0 and redis 3.2.0 #1018
Comments
I confirm this issue still exists in Kombu 4.5.0 and redis 3.2.1. Random broken pipe errors, as a result, my tasks random fail to start. |
Any updates? |
I am still having the issues in the latest branches of celery / kombu / redis So I am staying on the previous branches for now (celery 4.2 / kombu 4.3 / redispy 2.10) It seems the issue is coming from redispy 3.x branch, and using this redispy branch is required in new celery / kombu branches (celery 4.3+ / kombu 4.4) You can check the redis issue status there |
I've seen It before, but it looks like they are not going to fix it (as it's not an issue for them). |
This is a big issue for me as well. It looks like this was fixed on the redis-py side, but |
can you come with a PR @Frogger72 |
+1 |
Any updates? I am still havine the issue today |
celery version? |
I'm getting this error w/o celery in the mix. |
I was previously on kombu 4.3.0 and redis 2.10.6, and after upgrading to kombu 4.4.0 and redis 3.2.0 (manually cf issue #1016 ) I noticed an issue on one of my Django REST endpoint:
OperationalError: Error 32 while writing to socket. Broken pipe.
I am not sure if it's an actual issue in the new kombu / redis, or if I had an issue in my code that was silenced in the previous kombu / redis version
The endpoint is heavily used, and never had any issue, this issue popped up a few times since I upgraded, but the endpoint still works most of the times
Any ideas?
Edit: Celery version is 4.2.1
Here is the stack trace:
The text was updated successfully, but these errors were encountered: