#celery

hi looking for more info on celery.graph. The celery doc seem to have only api info... Any pointers

Hi, I have a django app(1.9) using Celery (3.1) and am having some issues - I can run the worker in debug mode and it shows it registers all my tasks properly, but then the worker exits with exit code 0 (no errors, etc.) any ideas as to why?

I'm using Kombu/db as the messaging queue

super low volume tasks

I'm converting a home-grown message task system to Celery. In the original a message was published with a routing key "post.created", which was routed to two queues in a topic exchange "post-upload" and "post-process" which are both bound to the "post.created" routing key. How would I replicate this in Celery?

Basically I want to trigger two tasks at the same time :)

Celery seems to have groups, but I'd prefer to define these kind of things in my routing..

or is this "unceleryic" :)

I'm running celery w/Django and when I run the worker in a shell, everything is fine - works great. However, when I launch it using "multi start MYAPP" I find that it uses all defaults (so it doesn't use the configured broker/creds) any ideas as to what the cause might be?

I'm using 4.0.0rc2 (to take advantage of the much-improved SQS broker) and I've recently (in the last 48 hours or so) found that my workers are slowly dying after around 30-40 minutes of expected activity. I've been through all the issues/SO questions I can find. Tried all possible solutions. strace and lsof have shown me that hung workers are trying to read from a pipe to celery. Any ideas?

erve: hard to debug with the sqs broker since we don't have remote control commands

when you say hung workers are reading from a pipe, do you mean the worker main process, or the child processes?

the child processes are supposed to be reading from pipes when they don't have work