we are using django and celery and 4 workers to achieve some tasks.
Sometimes, when we are running a quite long task (2 or 3 minutes), the task got killed by something, but we are not able to figure what.
Here is an extract of the log we got :
[2012-01-11 16:31:53,509: INFO/PoolWorker-1] haploid.createSendingTasks[46e8e...f8d]: get packet [2012-01-11 16:31:53,511: INFO/PoolWorker-1] haploid.createSendingTasks[46e8e...f8d]: create task! [2012-01-11 16:31:54,634: INFO/PoolWorker-2] child process calling self.run() [2012-01-11 16:31:54,654: INFO/PoolWorker-2] haploid.notifs.send.ios[c54...21b]: -- handle Ios Notif ! [2012-01-11 16:31:54,686: INFO/MainProcess] Got task from broker: haploid.send.packet[b40a...deb5]
Just after the log "create task" the task createSendingTasks disapeared and we got this message "child process calling self.run()"
We have some few particularities :
Does somebody have an idea about why the task got killed? And how to find why?
Could there be a link with an exit() on another worker ?
asked Jan 11 '12haploid
3 ● 3
I tried to change --time-limit and --maxtasksperchild settings but this doesn't seems to change anything
I tried to turn off events too
I have no more ideas, please help!
answered Jan 12 '12haploid
3 ● 3
Asked: Jan 11 '12
Seen: 90 times
Last updated: Jan 12 '12
Copyright DotCloud, 2011. Some rights reserved under creative commons license. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.