I don't know the solution, but we had the same problem. We ended up dumping Celery in favor of rq. It's much easier to work with and we were already using Redis as a back-end.
If you do figure out the solution to this, please post it here. Also, consider rq. We used Celery quite a bit and the changeover was fairly simple. For the record, the logging was not the main reason we dumped Celery. Workers were also mysteriously locking up for some reason, and we couldn't narrow it down to any of our tasks, nor even the async versus the cron-style tasks. This is after running Celery for over two years on the same server so it could be due to the evolution of our codebase rather than Celery, but we wasted too many hours on it to want to deal with it. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
