On 12/4/19 6:15 AM, actionmystique@gmail.com wrote:
Ubuntu 20.04 mailman3 3.2.2-1 python3-django-hyperkitty 1.3.0-1ubuntu1
According to Hyperkitty Asynchronous tasks paragraph, we can start a qcluster systemd service file: ... [Service] ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings User=<user> Group=<group> Restart=always
Did you replace <django_project_path>, <user> and <group> with appropriate values?
...
Starting it works fine: ... However, the service fails after a few seconds:
# systemctl status qcluster ● qcluster.service - HyperKitty async tasks runner Loaded: loaded (/etc/systemd/system/qcluster.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2019-12-04 15:09:48 CET; 1min 1s ago Process: 1055961 ExecStart=/usr/bin/django-admin qcluster --pythonpath <django_project_path> --settings settings (code=exited, status=1/FAILURE) Main PID: 1055961 (code=exited, status=1/FAILURE)
It appears you haven't replaced <django_project_path> with the actual path to the directory containing your Django settings.py file
Also, <user> and <group> should be those of the Mailman user, probably 'list' in Debian/Ubuntu packages.
...
Also, another doc paragraph Running the task queue (required) talks about another required command "python manage.py qcluster"; so which one is it?
They should be the same thing. Usually manage.py is just configured to run the django-admin command for the particular project.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan