AttributeError: 'module' object has no attribute 'celery'

Question

I am following the Celery Documentation v:latest I installed all the dependencies and my celery version is 3.0.11 I made a file tasks.py and pasted the code:

from celery import Celery

app = Celery('tasks', broker='amqp://guest@localhost//')

@app.task
def add(x, y):
    return x + y

When I run the very Next command in the same directory:

celery -A tasks worker --loglevel=info

I get this error `AttributeError: 'module' object has no attribute 'celery'

I got few similar question but that did not helped me ... Do any one has any idea ? Here is the TraceBack...

Traceback (most recent call last):
  File "/home/nishant-un/env/bin/celery", line 9, in <module>
    load_entry_point('celery==3.0.11', 'console_scripts', 'celery')()
  File "/home/nishant-un/env/local/lib/python2.7/site-packages/celery/__main__.py", line 14, in main
    main()
  File "/home/nishant-un/env/local/lib/python2.7/site-packages/celery/bin/celery.py", line 946, in main
    cmd.execute_from_commandline(argv)
  File "/home/nishant-un/env/local/lib/python2.7/site-packages/celery/bin/celery.py", line 890, in execute_from_commandline
    super(CeleryCommand, self).execute_from_commandline(argv)))
  File "/home/nishant-un/env/local/lib/python2.7/site-packages/celery/bin/base.py", line 177, in execute_from_commandline
    argv = self.setup_app_from_commandline(argv)
  File "/home/nishant-un/env/local/lib/python2.7/site-packages/celery/bin/base.py", line 295, in setup_app_from_commandline
    self.app = self.find_app(app)
  File "/home/nishant-un/env/local/lib/python2.7/site-packages/celery/bin/base.py", line 313, in find_app
    return sym.celery
AttributeError: 'module' object has no attribute 'celery'

On what line do you get that AttributeError? Could you provide a full traceback please? — Lukas Graf
– Lukas Graf, Commented Nov 17, 2013 at 10:17
Why are you using 3.0.11? Seems like you are using the example from Celery 3.1. You can always specify the full path to the app, which in your example would be: -A tasks:app This means the same as from tasks import app in a python module, and tells the celery command where to find the instance to use, the shortcut form did not work like this in the version you are using (3.0.11) — asksol
– asksol, Commented Nov 17, 2013 at 20:43

raratiru · Accepted Answer · 2015-09-16 12:18:16Z

12

Running the following command from the root of my project, fixed this issue:

celery -A my_app.tasks worker --loglevel=info

Celery needed the path to the tasks.py file.

answered Sep 16, 2015 at 12:18

raratiru

9,7864 gold badges83 silver badges119 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

alko · Accepted Answer · 2013-11-17 11:39:59Z

6

Try replace your code with

celery = Celery('tasks', broker='amqp://guest@localhost//')

@celery.task
def add(x, y):
    return x + y

answered Nov 17, 2013 at 11:39

alko

48.7k12 gold badges99 silver badges105 bronze badges

5 Comments

Nishant Kashyap Over a year ago

I did that But I am Getting another error after it starts: I am pasting it in breaks because it is too long.

[2013-11-17 17:21:47,020: ERROR/MainProcess] Received unregistered task of type 'task.messagecleaner.clean_message'. The message has been ignored and discarded. Did you remember to import the module containing this task? Or maybe you are using relative imports? Please see http://bit.ly/gLye1c for more information.

Nishant Kashyap Over a year ago

Traceback (most recent call last):   File "/home/nishant-un/env/local/lib/python2.7/site-packages/celery/worker/consumer.py", line 432, in on_task_received     strategies[name](message, body, message.ack_log_error) KeyError: 'task.messagecleaner.clean_message'

alko Over a year ago

@NishantKashyap do this error arise when you run task.add() task?

asksol Over a year ago

Your version is old, you should upgrade to 3.1

Brendan Wood Over a year ago

To expand on asksol's helpful comment, it appears that version of Celery prior to 3.1 required the Celery instance to be named exactly "celery", and OP's error is a result of this. This appears to have been changed in Celery 3.1, so it doesn't matter what you call your Celery instance.

Collectives™ on Stack Overflow

AttributeError: 'module' object has no attribute 'celery'

2 Answers 2

Comments

5 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

5 Comments

Your Answer

Sign up or log in

Post as a guest

Related