-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
UnexpectedFrame exception after "Connection to broker lost" #1779
Comments
Alright, I confirm the workers stop working (or crash) in 3.1.7, but I do not see this specific error in the log, so it might be something else |
Do you know how to reproduce the error? |
No. But we have celery deployed on 10-16 instances at the moment and it will happen to 1 or 2 of them every 24h. I am trying to identify which task might be related. I am not sure how to debug it, but if you have anything, let me know. Logging is on WARNING right now and it is all we see. |
I believe I'm seeing the same issue.
Running:
We see this issue sporadically in the production environment (Heroku, using BigWig as the amqp service). I haven't repro'ed the issue when running locally. I'll report back if I can gather more useful evidence. |
Is there any solution to this problem? I am seeing this typically, 1 -2 times per day across 6 different servers. [2014-09-08 10:05:32,491: WARNING/MainProcess] consumer: Connection to broker lost. Trying to re-establish the connection... Traceback (most recent call last): Running: |
This could be related to #2066. |
Closing this, as we don't have the resources to complete this task. |
Still an issue in Celery 4.3.0. |
Looking again, we have a very different stack trace. I think this is only related to Kombu, not Celery. Sorry for the noise. Here's the stack trace anyway, in case it's of interest:
|
can you also check celery master? with py-amqp master? |
To my knowledge, we've only seen this error once or twice in about 2 million server hours, and I have no reliable repro steps. Also these are production servers so unfortunately I'm unable to test. |
OK wait until test it with celery==4.4.0 |
can you test with celery==4.4.0 |
closing for now based on this scenario for now. but we will reopen it if this becomes more frequent. also #6416 might fix this, we will reopen it if it doesn;t. |
Hey, I am not sure if this is a duplicate or not, but I could not find this exact issue. I realize we are not running 3.1.7 so I will upgrade all machines to check
Running:
amqp==1.3.3
billiard==3.3.0.10
celery==3.1.6
eventlet==0.14.0
kombu==3.0.7
Getting the following issue:
The text was updated successfully, but these errors were encountered: