Why can't it find my celery config file?

2019-03-09 19:53发布

问题:

/home/myuser/mysite-env/lib/python2.6/site-packages/celery/loaders/default.py:53: NotConfigured: No celeryconfig.py module found! Please make sure it exists and is available to Python.
NotConfigured)

I even defined it in my /etc/profile and also in my virtual environment's "activate". But it's not reading it.

回答1:

I had a similar problem with my tasks module. A simple

# celery config is in a non-standard location
import os
os.environ['CELERY_CONFIG_MODULE'] = 'mypackage.celeryconfig'

in my package's __init__.py solved this problem.



回答2:

Now in Celery 4.1 you can solve that problem by that code(the easiest way):

import celeryconfig

from celery import Celery

app = Celery()
app.config_from_object(celeryconfig)

For Example small celeryconfig.py :

BROKER_URL = 'pyamqp://'
CELERY_RESULT_BACKEND = 'redis://localhost'
CELERY_ROUTES = {'task_name': {'queue': 'queue_name_for_task'}}

Also very simple way:

from celery import Celery

app = Celery('tasks')

app.conf.update(
    result_expires=60,
    task_acks_late=True,
    broker_url='pyamqp://',
    result_backend='redis://localhost'
)

Or Using a configuration class/object:

from celery import Celery

app = Celery()

class Config:
    enable_utc = True
    timezone = 'Europe/London'

app.config_from_object(Config)
# or using the fully qualified name of the object:
#   app.config_from_object('module:Config')

Or how was mentioned by setting CELERY_CONFIG_MODULE

import os
from celery import Celery

#: Set default configuration module name
os.environ.setdefault('CELERY_CONFIG_MODULE', 'celeryconfig')

app = Celery()
app.config_from_envvar('CELERY_CONFIG_MODULE')

Also see:

  • Create config: http://docs.celeryproject.org/en/latest/userguide/application.html#configuration
  • Configuration fields: http://docs.celeryproject.org/en/latest/userguide/configuration.html


回答3:

Make sure you have celeryconfig.py in the same location you are running 'celeryd' or otherwise make sure its is available on the Python path.



回答4:

you can work around this with the environment... or, use --config: it requires

  1. a path relative to CELERY_CHDIR from /etc/defaults/celeryd
  2. a python module name, not a filename.

The error message could probably use these two facts.