Python celery

For configuration files, the directory /etc/celery/ needs to be created with a configuration file named app.conf where app is the name of your application. An example configuration file is provided within Celery documentation.

Start/enable the celery@app.service.

To run celery in a virtualenv, make a copy of celery@.service in /etc/systemd/system so you can customize it, and change the paths of the celery binary to the copy in your virtualenv.

RabbitMQ stores its configuration within /etc/rabbitmq/rabbitmq-env.conf

You probably want to replace with , RabbitMQ does not support Unix sockets.

For simple configurations, you may also want to add . Read more about environmental variables within RabbitMQ docs

Start/enable .

Follow RabbitMQ documentation and add your user and virtual host:

$ cd /var/lib/rabbitmq
$ su rabbitmq -c 'rabbitmqctl add_user myuser mypassword'
$ su rabbitmq -c 'rabbitmqctl add_vhost myvhost'
$ su rabbitmq -c 'rabbitmqctl set_user_tags myuser mytag'
$ su rabbitmq -c 'rabbitmqctl set_permissions -p myvhost myuser ".*" ".*" ".*"'

Read the RabbitMQ admin guide to understand the above.

If issuing results in badrpc,nodedown visit this blog post for more information how to fix the problem.

You may want to read a security section from relevant Celery documentation

Follow Celery documentation to create a python sample task:

Use the same credentials/vhost you have created when configuring RabbitMQ

- this parameter is optional since RabbitMQ is the default broker utilised by celery.

While in the same directory as your you can run:

$ celery -A task worker --loglevel=info

Then from another console (but within same directory) create:

Run it:

$ python call.py

First, the console should log some information suggesting worker was called:

Received task: task.add[f4aff99a-7477-44db-9f6e-7e0f9342cd4e]
Task task.add[f4aff99a-7477-44db-9f6e-7e0f9342cd4e] succeeded in 0.0007182330009527504s: 8

Procedure below is slightly different than what you will find within Celery documentation

To make the module as root, create first the directory, a blank and the following files should be created inside of it:

/lib/python3.5/site-packages/test_task/test_task.py

from __future__ import absolute_import

from test_task.celery import app

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

At this point if you issue python in your console you should be able to issue following without any error:

>>> from test_task import celery

In replace:

CELERY_APP="proj"

with the following line:

CELERY_APP="test_task"

Restart the .

Tasks can be ran periodicaly through Celery Beat, basic setup is described within relevant Celery documentation pages. An example:

If you want to specify within your , then you need to add the prefix to make celery recognise your scheduled tasks. After that you need to add the parameters when you start the celery daemon. Further, the directory must exist within the celery-relevant environment and be owned by the user that runs celery.