Are you using upstart or surveillance or something else to work with celery + celery beating as background tasks? In production, you must use one of them in order to run celery workers + celery bikini in the background.
The easiest way to check how celery shoot works: ps aux | grep -i '[c]elerybeat' ps aux | grep -i '[c]elerybeat' . If you get a text string with pid , it works. You can also make the output of this command prettier: ps aux | grep -i '[c]elerybeat' | awk '{print $2}' ps aux | grep -i '[c]elerybeat' | awk '{print $2}' ps aux | grep -i '[c]elerybeat' | awk '{print $2}' . If you get a number, it works; if you don't get anything, it doesn't work.
You can also check the status of celery workers: celery -A projectname status .
If you are interested in advanced celery monitoring, you can read the official monitoring documentation.
valex
source share