seconds. Key eviction Redis may evict keys from the database in some situations If you experience an error like: InconsistencyError: Probably the key ('_kombu.binding.celery') has been removed from the Redis Keeping Results Configuration Where to go from here Troubleshooting Worker doesn’t start: Permission Error Result backend doesn’t work or tasks are always in PENDING state Choosing a Broker Celery requires also a troubleshooting section in the Frequently Asked Questions. Worker doesn’t start: Permission Error If you’re using Debian, Ubuntu or other Debian-based distributions: Debian recently renamed the

seconds. Key eviction Redis may evict keys from the database in some situations If you experience an error like: InconsistencyError: Probably the key ('_kombu.binding.celery') has been removed from the Redis Keeping Results Configuration Where to go from here Troubleshooting Worker doesn’t start: Permission Error Result backend doesn’t work or tasks are always in PENDING state Choosing a Broker Celery requires also a troubleshooting section in the Frequently Asked Questions. Worker doesn’t start: Permission Error If you’re using Debian, Ubuntu or other Debian-based distributions: Debian recently renamed the

seconds. Key eviction Redis may evict keys from the database in some situations If you experience an error like: InconsistencyError: Probably the key ('_kombu.binding.celery') has been removed from the Redis Keeping Results Configuration Where to go from here Troubleshooting Worker doesn’t start: Permission Error Result backend doesn’t work or tasks are always in PENDING state Choosing a Broker Celery requires also a troubleshooting section in the Frequently Asked Questions. Worker doesn’t start: Permission Error If you’re using Debian, Ubuntu or other Debian-based distributions: Debian recently renamed the

seconds. Key eviction Redis may evict keys from the database in some situations If you experience an error like: InconsistencyError: Probably the key ('_kombu.binding.celery') has been removed from the Redis Keeping Results Configuration Where to go from here Troubleshooting Worker doesn’t start: Permission Error Result backend doesn’t work or tasks are always in PENDING state Choosing a Broker Celery requires also a troubleshooting section in the Frequently Asked Questions. Worker doesn’t start: Permission Error If you’re using Debian, Ubuntu or other Debian-based distributions: Debian recently renamed the

RabbitMQ, Stomp, Redis, and most common SQL databases. Robust Using RabbitMQ, celery survives most error scenarios, and your tasks will never be lost. Dis- tributed Runs on one or more machines. Supports You can query status and results via URLs, enabling the ability to poll task status using Ajax. Error e-mails Can be configured to send e-mails to the administrators when tasks fails. Super- vised results. Task.send_error_emails Send an e-mail whenever a task of this type fails. Defaults to the CELERY_SEND_TASK_ERROR_EMAILS setting. See Error E-Mails for more information. Task.error_whitelist If the

RabbitMQ, Stomp, Redis, and most common SQL databases. Robust Using RabbitMQ, celery survives most error scenarios, and your tasks will never be lost. Distributed Runs on one or more machines. Supports You can query status and results via URLs, enabling the ability to poll task status using Ajax. Error e-mails Can be configured to send e-mails to the administrators when tasks fails. Supervised Pool results. Task.send_error_emails Send an e-mail whenever a task of this type fails. Defaults to the CELERY_SEND_TASK_ERROR_EMAILS setting. See Error E-Mails for more information. Task.error_whitelist If the

seconds. Key eviction Redis may evict keys from the database in some situations If you experience an error like: InconsistencyError: Probably the key ('_kombu.binding.celery') has been removed from the Redis Keeping Results Configuration Where to go from here Troubleshooting Worker doesn’t start: Permission Error Result backend doesn’t work or tasks are always in PENDING state Choosing a Broker Celery requires also a troubleshooting section in the Frequently Asked Questions. Worker doesn’t start: Permission Error If you’re using Debian, Ubuntu or other Debian-based distributions: Debian recently renamed the

seconds. Key eviction Redis may evict keys from the database in some situations If you experience an error like: InconsistencyError: Probably the key ('_kombu.binding.celery') has been removed from the Redis Keeping Results Configuration Where to go from here Troubleshooting Worker doesn’t start: Permission Error Result backend doesn’t work or tasks are always in PENDING state Choosing a Broker Celery requires also a troubleshooting section in the Frequently Asked Questions. Worker doesn’t start: Permission Error If you’re using Debian, Ubuntu or other Debian-based distributions: Debian recently renamed the

database number. • Redis may evict keys from the database in some situations If you experience an error like: InconsistencyError, Probably the key ('_kombu.binding.celery') has been removed from the Redis Release 3.1.25 • Where to go from here • Troubleshooting – Worker does not start: Permission Error – Result backend does not work or tasks are always in PENDING state. – Segmentation fault at start also a troubleshooting section in the Frequently Asked Questions. Worker does not start: Permission Error • If you’re using Debian, Ubuntu or other Debian-based distributions: 2.2. Getting Started 29 Celery

database number. Redis may evict keys from the database in some situations If you experience an error like: InconsistencyError, Probably the key ('_kombu.binding.celery') has been removed from the Redis Keeping Results Configuration Where to go from here Troubleshooting Worker does not start: Permission Error Result backend does not work or tasks are always in PENDING state. Segmentation fault at start when also a troubleshooting section in the Frequently Asked Questions. Worker does not start: Permission Error If you’re using Debian, Ubuntu or other Debian-based distributions: Debian recently renamed the