libretime/worker
Jonas L 30b3470a06
Better format enforcing (#1391)
* Add shared python format-check target

* Add .format-check to api lint target

* Format api code with makefile format target

* Add .format-check to tools lint target

* Add .format-check to analyzer lint target

* Format analyzer code with makefile format target

* Add .format-check to celery lint target

* Add .format-check to api_client lint target

* Format api_client code with makefile format target

* Add .format-check to playout lint target

* Run CI linting in parallel

* Disable isort in pre-commit
2021-10-17 16:24:37 +02:00
..
airtime-celery Move python_apps/airtime-celery/ to worker/ 2021-10-17 08:02:47 +00:00
install/systemd Move python_apps/airtime-celery/ to worker/ 2021-10-17 08:02:47 +00:00
Makefile Better format enforcing (#1391) 2021-10-17 16:24:37 +02:00
README.md Move python_apps/airtime-celery/ to worker/ 2021-10-17 08:02:47 +00:00
setup.py Move python_apps/airtime-celery/ to worker/ 2021-10-17 08:02:47 +00:00

README.md

airtime-celery

airtime-celery is a Celery daemon for handling backend tasks asynchronously. Communication and the Celery results backend are both handled with amqp (RabbitMQ).

Installation

sudo python3 setup.py install

Each instance of airtime-celery has its own worker, and multiple instances can be run in parallel. Celery is thread-safe, so this parallelization won't cause conflicts.

Developers

To debug, you can run celery directly from the command line:

RMQ_CONFIG_FILE=${LIBRETIME_CONF_DIR}/airtime.conf celery -A airtime-celery.tasks worker --loglevel=info

This worker can be run alongside the service without issue.

You may want to use the setuptools develop target to install:

sudo python setup.py develop

You will need to allow the "airtime" RabbitMQ user to access all exchanges and queues within the /airtime vhost:

sudo rabbitmqctl set_permissions -p /airtime airtime .\* .\* .\*

Logging

By default, logs are saved to:

/var/log/airtime/airtime-celery[-DEV_ENV].log

Troubleshooting

If you run into issues getting Celery to accept tasks from Airtime:

  1. Make sure Celery is running ($ sudo service airtime-celery status).
  2. Check the log file (/var/log/airtime/airtime-celery[-DEV_ENV].log) to make sure Celery started correctly.
  3. Check your $LIBRETIME_CONF_DIR/airtime.conf rabbitmq settings. Make sure the settings here align with $LIBRETIME_CONF_DIR/$ENVIRONMENT/rabbitmq.ini.
  4. Check RabbitMQ to make sure the celeryresults and task queues were created in the correct vhost.
  5. Make sure the RabbitMQ user (the default is airtime) has permissions on all vhosts being used.