Celery messes with the error a bit but it still propagates the full original traceback. What I mean is that if you change the value of error_msg from "Task %(name)s[%(id)s] %(description)s: %(exc)s" to "Task %(name)s[%(id)s] %(description)s: %(traceback)s" in /usr/lib/python2.7/dist-packages/celery/worker/job.py:Request you'll see the full error message when a task fails.
We could do this by either monkey patching celery or registering a new log handler.
Here is the idea I had on how to fix the bug:
Celery messes with the error a bit but it still propagates the full original traceback. What I mean is that if you change the value of error_msg from "Task %(name)s[%(id)s] %(description)s: %(exc)s" to "Task %(name)s[%(id)s] %(description)s: %(traceback)s" in /usr/lib/ python2. 7/dist- packages/ celery/ worker/ job.py: Request you'll see the full error message when a task fails.
We could do this by either monkey patching celery or registering a new log handler.