[systemd-devel] Is this list still active? Where can I get basic help with systemd

[Andrei Borzenkov]

03.12.2017 04:40, Doug Snyder пишет:
> I'm trying to write a basic systemd service. The ExecStart command I'm
> using works. The systemd service doesn't. It throws a cryptic error and I
> can't find any documentation on the web that makes any sense of it. I
> posted on this list and got no responses. Is this list active? If not is
> there somewhere I can get basic help for setting up a service. Systemd is
> the default tool daemonizing on most Linux distros right? There must be
> some way to get help to get a basic example working.
> 
> 
> My previous email:
> 
> I am trying to create a systemd service to manage the celery task queue
> 
> My service file is :
> [Unit]
> Description=Celery bf Service
> After=network.target
> 
> [Service]
> Type=forking
> User=doug
> Group=doug
> WorkingDirectory=/home/doug/www/my_project
> ExecStart=/home/doug/.virtualenvs/bf-env/bin/celery    -A tasks worker
>  --app=tasks.celery_app:app   --logfile=/var/log/celery/bf/%n%I.log
>  --loglevel=INFO   -Ofair --time-limit=300
> 
> When I run:
> $ systemctl start celery_bf.service
> I get:
> Job for celery_bf.service failed because a configured resource limit was

This cryptic message was changed more than a year ago which suggests you
are running older distribution release.

> exceeded. See "systemctl status celery_bf.service" and "journalctl -xe" for
> details.
> 
> $ systemctl status celery_bf.service
> ● celery_bf.service - Celery bf Service
>    Loaded: loaded (/etc/systemd/system/celery_bf.service; enabled; vendor
> preset: disabled)
>    Active: failed (Result: resources)
> 
> Nov 20 13:57:20 stower systemd[1]: celery_bf.service failed.
> Nov 20 13:57:20 stower systemd[1]: Starting Celery bf Service...
> Nov 20 13:58:33 stower systemd[1]: celery_bf.service failed to run 'start'
> task: Operation not supported

This is really catch-all message. Try to enable systemd debug output, it
may provide more information; anything in application logs; anything in
journal around this event (you show only messages directly related to
service, but execution may be blocked by apparmor, selinux etc).