Django Celery - running scheduled tasks -

After several hours on this without the result, I really need help

I'm able to run Django-Celery with my Django app and I scheduled tasks on it:

  dragon manage.py celeryd -E -B -l INFO  

Now it is time to produce and here it is that my pain begins. I have configured the cellarid as the daemon, it works, but scheduled tasks will not work.

So I added -b to CELERYD_OPTS . My tasks are now run as scheduled, but these are the boring lines on my logs:

  [2014-02-17 22: 37: 30,738: debuts / main process] Beat: 5.00 Waking in seconds  

I just want to delete that line from my logs! I did not even understand what it meant.

So I had configured the Selerbeat daemon, thinking it would be a cleaner and suggest a solution to the production environment.

Unfortunately, when I stop the celerybeat daemon, it creates a log and a PID file but scheduled tasks do not work. Info / main process] green: ... [2014-02-17 19: 15: 41,921: information / main process] write entries. .. [2014-02-17 19: 15: 42,072: debug / main process] Current schedule: & lt; Model entry: Salary. Backendclub cellar Backend_clank (* [], ** {}) {4} & gt; & Lt; Model entry: MyApp.tasks.test_task MyApp.tasks.test_task (* [], ** {}) {4} & gt; [2014-02-17 19: 15: 42,187: Debuts / Main Procedure] Beat: Tick with maximum interval -> 5.00 seconds [2014-02-17 19:15:15 42,206: debug / main process] Start with server, version: 0.9, Properties: {u'information ': UI license under UL See http://www.rabbitmq.com/ ', u'product': u'RabbitMQ ', u'copyright': u'Copyright (c) 2007-2011 VMware, Inc. ', U'capabilities': {U' Exchange_exchange_bindings': True, u'common_connel_notify ': True, you' Publisher_Germants': True, U'besic. En ': True}, U' Platform ': U'arling / OTP', U 'version': U '2.7 1'}, Technique: [u'len ', u' mcupline '], locale: [u'en_US '] [2014-02-17 19: 15: 42,207: debuts / main process] Open OK! [2014-02-17 19: 15: 42,257: info / main process] Scheduler: sending my work to MyApp.tasks.test_task (MyApp.tasks.test_task)

and nothing else.

I understand everything works well (rabbits are included in the MQ, whose logs are clean and without errors)

I just want to log on to my log file with long useless lines Need to avoid clean and quick solutions

Can anyone help? Thanks !!

I resolved to disable this problem in the django-debug-toolbar in the production environment.

It seems that DjJo-Celli and Django-Debug-Toolbar can sometimes mess up the logging configuration.