<div dir="ltr">Well, it runs fine by itself using the exact same command on the command line.<div>Its when systemd is added to the mix that the problems occur</div><div>The people that put out celery have docs on how to use it with systemd, its just that they don't work:</div><div><a href="http://docs.celeryproject.org/en/latest/userguide/daemonizing.html">http://docs.celeryproject.org/en/latest/userguide/daemonizing.html</a> </div><div>I based my service off theirs but the Type=forking was copied right from theirs</div><div>Maybe if I use their version more exactly it might work.</div><div>But their version doesn't work at all ssince I suspect they are using templating</div><div>( I copied the %I from their file )</div><div>They reference config variables in their template:</div><div> </div><div><code class="gmail-file gmail-docutils gmail-literal" style="color:rgb(62,67,73);font-size:17px">/etc/systemd/system/celery.service</code>: </div><div><pre style="overflow-x:auto;overflow-y:hidden;font-family:Consolas,Menlo,"Deja Vu Sans Mono","Bitstream Vera Sans Mono",monospace;font-size:0.9em;background:rgb(240,255,235);padding:7px 10px;margin-top:15px;margin-bottom:15px;border:1px solid rgb(199,236,184);border-radius:2px;line-height:1.3em;color:rgb(62,67,73)">[Unit] Description=Celery Service After=network.target [Service] Type=forking User=celery Group=celery EnvironmentFile=-/etc/conf.d/celery WorkingDirectory=/opt/celery ExecStart=/bin/sh -c '${CELERY_BIN} multi start ${CELERYD_NODES} \ -A ${CELERY_APP} --pidfile=${CELERYD_PID_FILE} \ --logfile=${CELERYD_LOG_FILE} --loglevel=${CELERYD_LOG_LEVEL} ${CELERYD_OPTS}' ExecStop=/bin/sh -c '${CELERY_BIN} multi stopwait ${CELERYD_NODES} \ --pidfile=${CELERYD_PID_FILE}' ExecReload=/bin/sh -c '${CELERY_BIN} multi restart ${CELERYD_NODES} \ -A ${CELERY_APP} --pidfile=${CELERYD_PID_FILE} \ --logfile=${CELERYD_LOG_FILE} --loglevel=${CELERYD_LOG_LEVEL} ${CELERYD_OPTS}' [Install] WantedBy=multi-user.target</pre><pre style="overflow-x:auto;overflow-y:hidden;font-family:Consolas,Menlo,"Deja Vu Sans Mono","Bitstream Vera Sans Mono",monospace;font-size:0.9em;background:rgb(240,255,235);padding:7px 10px;margin-top:15px;margin-bottom:15px;border:1px solid rgb(199,236,184);border-radius:2px;line-height:1.3em;color:rgb(62,67,73)"><div class="gmail-section" id="example-configuration" style="font-family:Optima,Segoe,"Segoe UI",Candara,Calibri,Arial,sans-serif;font-size:17px;white-space:normal;background-color:rgb(255,255,255)"><code class="gmail-file gmail-docutils gmail-literal">/etc/default/celeryd</code>:<div class="gmail-highlight-bash"><div class="gmail-highlight" style="background-image:initial;background-position:initial;background-size:initial;background-repeat:initial;background-origin:initial;background-clip:initial"><pre style="overflow-x:auto;overflow-y:hidden;font-family:Consolas,Menlo,"Deja Vu Sans Mono","Bitstream Vera Sans Mono",monospace;font-size:0.9em;background:rgb(240,255,235);padding:7px 10px;margin-top:15px;margin-bottom:15px;border:1px solid rgb(199,236,184);border-radius:2px;line-height:1.3em"># Names of nodes to start # most people will only start one node: CELERYD_NODES="worker1" # but you can also start multiple and configure settings # for each in CELERYD_OPTS #CELERYD_NODES="worker1 worker2 worker3" # alternatively, you can specify the number of nodes to start: #CELERYD_NODES=10 # Absolute or relative path to the 'celery' command: CELERY_BIN="/usr/local/bin/celery" #CELERY_BIN="/virtualenvs/def/bin/celery" # App instance to use # comment out this line if you don't use an app CELERY_APP="proj" # or fully qualified: #CELERY_APP="proj.tasks:app" # Where to chdir at start. CELERYD_CHDIR="/opt/Myproject/" # Extra command-line arguments to the worker CELERYD_OPTS="--time-limit=300 --concurrency=8" # Configure node-specific settings by appending node name to arguments: #CELERYD_OPTS="--time-limit=300 -c 8 -c:worker2 4 -c:worker3 2 -Ofair:worker1" # Set logging level to DEBUG #CELERYD_LOG_LEVEL="DEBUG" # %n will be replaced with the first part of the nodename. CELERYD_LOG_FILE="/var/log/celery/%n%I.log" CELERYD_PID_FILE="/var/run/celery/%n.pid" # Workers should run as an unprivileged user. # You need to create this user manually (or you can choose # a user/group combination that already exists (e.g., nobody). CELERYD_USER="celery" CELERYD_GROUP="celery" # If enabled pid and log directories will be created if missing, # and owned by the userid/group configured. CELERY_CREATE_DIRS=1 </pre><pre style="overflow-x:auto;overflow-y:hidden;font-family:Consolas,Menlo,"Deja Vu Sans Mono","Bitstream Vera Sans Mono",monospace;font-size:0.9em;background:rgb(240,255,235);padding:7px 10px;margin-top:15px;margin-bottom:15px;border:1px solid rgb(199,236,184);border-radius:2px;line-height:1.3em">But nowhere in their documentation is any mention of the fact that they are using templates or how how make a service a template.</pre><pre style="overflow-x:auto;overflow-y:hidden;font-family:Consolas,Menlo,"Deja Vu Sans Mono","Bitstream Vera Sans Mono",monospace;font-size:0.9em;background:rgb(240,255,235);padding:7px 10px;margin-top:15px;margin-bottom:15px;border:1px solid rgb(199,236,184);border-radius:2px;line-height:1.3em"> Is there docs on this you can point me to? Or if not just explain it?</pre><pre style="overflow-x:auto;overflow-y:hidden;font-family:Consolas,Menlo,"Deja Vu Sans Mono","Bitstream Vera Sans Mono",monospace;font-size:0.9em;background:rgb(240,255,235);padding:7px 10px;margin-top:15px;margin-bottom:15px;border:1px solid rgb(199,236,184);border-radius:2px;line-height:1.3em"> </pre></div></div></div><div class="gmail-section" id="gmail-using-a-login-shell" style="font-family:Optima,Segoe,"Segoe UI",Candara,Calibri,Arial,sans-serif;font-size:17px;white-space:normal;background-color:rgb(255,255,255)"></div></pre></div><div class="gmail_extra"> <div class="gmail_quote">On Tue, Dec 5, 2017 at 1:50 PM, Lennart Poettering <<a href="mailto:lennart@poettering.net" target="_blank">lennart@poettering.net</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Di, 05.12.17 13:33, Doug Snyder (<a href="mailto:webcoach101@gmail.com">webcoach101@gmail.com</a>) wrote: > Getting rid of the template syntax changed the behavior but now it appears > there's another problem I don't understand. > it tries to start the unit and it shows some encouraging signs but fails > because a timeout was exceeded. > Celery starts and shows healthy output but then sends a SIGCHLD and then > dies Uh, I am not sure what celery is, but if celery is started but exits on its own then I am not sure I can help you very much. > I don't know if you know what celery is but its a task queue so it does > create child processes > I thought the Type=forking line in the service unit would let systemd about > that. > Or maybe its dying for some other reason? > It works fine when run without systemd Does it detach on its own? i.e. double fork? if yes, then type=forking is the right choice, otherwise you need a different Type=. > I don't think I can send you detailed output until we get this issue > resolved with the mailing list and why its not excepting emails with debug > output. > Short emails seem to post. Long ones don't. There's no indication of whats > going on There are message size limits on this mailing list. Please condense your logs to only include relevant bits hence, or use <a href="http://fpaste.org" rel="noreferrer" target="_blank">fpaste.org</a> or something like that, and drop the URL. <div class="HOEnZb"><div class="h5"> Lennart -- Lennart Poettering, Red Hat </div></div></blockquote></div> </div></div>