Unable to see celery magazines while running

Question

I start celery through supervisord, see the entry below.

[program:celery] user = foobar autostart = true autorestart = true directory = /opt/src/slicephone/cloud command = /opt/virtenvs/django_slice/bin/celery beat --app=cloud -l DEBUG -s /home/foobar/run/celerybeat-schedule --pidfile=/home/foobar/run/celerybeat.pid priority = 100 stdout_logfile_backups = 0 stderr_logfile_backups = 0 stdout_logfile_maxbytes = 10MB stderr_logfile_maxbytes = 10MB stdout_logfile = /opt/logs/celery.stdout.log stderr_logfile = /opt/logs/celery.stderr.log 

pipette freezing | grep celery

 celery==3.1.0 

But any use:

 @celery.task def test_rabbit_running(): import logging from celery.utils.log import get_task_logger logger = get_task_logger(__name__) logger.setLevel(logging.DEBUG) logger.info("foobar") 

not displayed in logs. Instead, I get entries like the following.

celery.stdout.log

 celery beat v3.1.0 (Cipater) is starting. __ - ... __ - _ Configuration -> . broker -> redis://localhost:6379// . loader -> celery.loaders.app.AppLoader . scheduler -> celery.beat.PersistentScheduler . db -> /home/foobar/run/celerybeat-schedule . logfile -> [stderr]@%DEBUG . maxinterval -> now (0s) 

celery.stderr.log

 [2013-11-12 05:42:39,539: DEBUG/MainProcess] beat: Waking up in 2.00 seconds. INFO Scheduler: Sending due task test_rabbit_running (retail.tasks.test_rabbit_running) [2013-11-12 05:42:41,547: INFO/MainProcess] Scheduler: Sending due task test_rabbit_running (retail.tasks.test_rabbit_running) DEBUG retail.tasks.test_rabbit_running sent. id->34268340-6ffd-44d0-8e61-475a83ab3481 [2013-11-12 05:42:41,550: DEBUG/MainProcess] retail.tasks.test_rabbit_running sent. id->34268340-6ffd-44d0-8e61-475a83ab3481 DEBUG beat: Waking up in 6.00 seconds. 

What do I need to do so that my log calls appear in the log files?

Answer 1

It does not record anything because it does not perform any tasks (and this is normal).

See also Celerybeat does not perform periodic tasks.

Answer 2

I would try to put a call to the log inside the task, since the util function name implies get_task_logger or it just starts with a simple print or it creates its own log, as suggested in Django's best tree logging practice (best way to go to IMO)