-
Notifications
You must be signed in to change notification settings - Fork 250
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
Crashes with broken pipe #16
Comments
We are observing similar problems on:
When running:
But it does not happen when run as:
or:
|
OK, it seems that with |
I am also seeing this error with the latest stable release where celery crashes after a few hours of long running tasks. I'm seeing this happen after an hour long job has timed out. [2012-10-22 03:22:13,673: WARNING/PoolWorker-1] Process PoolWorker-1: software -> celery:3.0.11 (Chiastic Slide) kombu:2.4.7 py:2.6.6 BROKER_URL: 'amqp://something/myvhost' |
@9thbit How did it time out? And do you think it's relevant? |
@ask I was simply monitoring the tasks using I have added |
I am using 2.7 and I am getting this. |
Python 2.7 here with |
Seeing this too with |
Same issue for us. |
Same issue here. |
Could you please include the version your are using? Also what broker are you using? (kombu is not a transport, it's the messaging framework we use) The latest celery version disabled force_execv by default, it could be a culprit. |
If you're using RabbitMQ/redis, could you please try running with |
I'm are also seeing this crash. I also tried the
Here's our
|
@jdp what celery/billiard version is this? please include the output of |
If this happens while flushing stdout, then it may be worth a try to simply ignore this error. |
Closing this issue now, please open a new issue if this happen again. Chances are it's not the same issue as the previous one. |
I met the same problem. I got this.It confused me for one week.. |
which version are you using? |
This makes our workers crash/hang every hour or so.
celery==3.0.7
django-celery==3.0.4
kombu==2.4.3
billiard==2.7.3.12
We're using the SQS backend.
The text was updated successfully, but these errors were encountered: