Start celery daemon via systemd

pythonsystemd

In the /usr/lib/systemd/system/celery.service:

[Unit]
Description=Celery Nodes Daemon
After=network.target

[Service]
Type=forking
PIDFile=/var/run/celery/main.pid
ExecStart=/usr/bin/python2 /home/myuser/path/to/Django/myproject/manage.py celeryd_multi start w1 --pidfile="/var/run/celery/%n.pid" --logfile="/var/log/celery/%n.log" --cmd="-m celery.bin.celeryd_detach"
ExecStop=/usr/bin/python2 /home/myuser/path/to/Django/myproject/manage.py celeryd_multi stopwait w1 --pidfile="/var/run/celery/%n.pid"

[Install]
WantedBy=multi-user.target

In the shell:

$ sudo systemctl enable celery.service
ln -s '/usr/lib/systemd/system/celery.service' '/etc/systemd/system/multi-user.target.wants/celery.service'
$ sudo systemctl start celery.service
Job for celery.service failed. See 'systemctl status celery.service' and 'journalctl -xn' for details.
$ sudo systemctl status celery.service
celery.service - Celery Nodes Daemon
  Loaded: loaded (/usr/lib/systemd/system/celery.service; enabled)
  Active: failed (Result: exit-code) since Пт 2013-03-29 13:22:24 NOVT; 38s ago
  Process: 32273 ExecStart=/usr/bin/python2 /home/anarchist/Desktop/Develop/Django/myproject/manage.py celeryd_multi start w1 --pidfile="/var/run/celery/%n.pid" --logfile="/var/log/celery/%n.log" --cmd="-m celery.bin.celeryd_detach" (code=exited, status=1/FAILURE)

In journalctl -xn nothing about celery. How to start the celery daemon via systemd?

Best Answer

After a whole bunch of experimenting i came up with this configuration for the service (modified to match your example):

[Unit]
Description=Celery Server
After=network.target

[Service]
Type=oneshot
KillMode=control-group
RemainAfterExit=yes
Restart=no
ExecStart=/usr/bin/python2 /home/myuser/path/to/Django/myproject/manage.py celeryd_multi start w1 --pidfile="/tmp/%n.pid" --logfile="/var/log/celery/%n.log" --loglevel=INFO --time-limit=300
ExecStop=/usr/bin/python2 /home/myuser/path/to/Django/myproject/manage.py celeryd_multi stopwait w1 --pidfile="/tmp/%n.pid"

[Install]
WantedBy=multi-user.target

Related Solutions

Linux – Systemd service start error

I'm assuming you have checked nothing else is using port 80 (which I assume lighttpd is configured to use). Check that bonescript still doesn't have the port bound, stop it with:

systemctl stop bonescript.service
systemctl stop bonescript.socket

Systemctl Service ‘systemd-modules-load’ Fails – How to Diagnose

I too had this issue. I was able to solve it by following the instructions on the Arch Linux systemd wiki page. Here is a summary of what I did :

Lets find the systemd services which fail to start

$ systemctl --failed  
------------------------------------------------------------------------
systemd-modules-load.service   loaded failed failed  Load Kernel Modules

Ok, we found a problem with systemd-modules-load service. We want to know more.

$ systemctl status systemd-modules-load  
------------------------------------------------------------------------
systemd-modules-load.service - Load Kernel Modules      
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)     
   Active: failed (Result: exit-code) since So 2013-08-25 11:48:13 CEST; 32s ago  
     Docs: man:systemd-modules-load.service(8).  
           man:modules-load.d(5)
  Process: 15630 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)

If the Process ID is not listed, just restart the failed service with

$ systemctl restart systemd-modules-load

Now we have the process id (PID) to investigate this error in depth. Enter the following command with the current Process ID (here: 15630):

$ journalctl _PID=15630
----------------------------------------------------------------------
-- Logs begin at Sa 2013-05-25 10:31:12 CEST, end at So 2013-08-25 11:51:17 CEST. --
Aug 25 11:48:13 mypc systemd-modules-load[15630]: Failed to find module 'blacklist usblp'
Aug 25 11:48:13 mypc systemd-modules-load[15630]: Failed to find module 'install usblp /bin/false'

We see that some of the kernel module configs have wrong settings. Therefore we have a look at these settings in /etc/modules-load.d/

$ ls -Al /etc/modules-load.d/
----------------------------------------------------------------------
...  
-rw-r--r--   1 root root    79  1. Dez 2012  blacklist.conf  
-rw-r--r--   1 root root     1  2. Mär 14:30 encrypt.conf  
-rw-r--r--   1 root root     3  5. Dez 2012  printing.conf  
-rw-r--r--   1 root root     6 14. Jul 11:01 realtek.conf  
-rw-r--r--   1 root root    65  2. Jun 23:01 virtualbox.conf  
...

The Failed to find module 'blacklist usblp' error message might be related to a wrong setting inside of blacklist.conf. Lets deactivate it with inserting a trailing # before each option we found via step 3:
```
/etc/modules-load.d/blacklist.conf  
----------------------------------------------------------------------
# blacklist usblp  
# install usblp /bin/false  
```

Now, try to start systemd-modules-load:

$ systemctl restart systemd-modules-load

If it was successful, this should not prompt anything. If you see any error, go back to step 3 and use the new PID for solving the errors left.

If everything is ok, you can verify that the service was started successfully with:

$ systemctl status systemd-modules-load
----------------------------------------------------------------------
systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
   Active: active (exited) since So 2013-08-25 12:22:31 CEST; 34s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
 Process: 19005 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
Aug 25 12:22:31 mypc systemd[1]: Started Load Kernel Modules.

Best Answer

Related Solutions

Linux – Systemd service start error

Systemctl Service ‘systemd-modules-load’ Fails – How to Diagnose

Related Question