You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
set up celery via systemd according to the celery docs
start celery via sudo service <your-celery-service-name> start
try to reload celery via sudo service <your-celery-service-name> reload
Expected behavior
Celery should gracefully reload.
Actual behavior
Celery does not gracefully reload. It shuts down, but never restarts.
After issuing the reload request (and subsequent failure to start), the output of sudo journalctl -xe doesn't seem to show anything nefarious:
Nov 15 04:33:04 ip-172-31-44-219 sudo[12972]: ubuntu : TTY=pts/0 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/sbin/service myproj-celery reload
Nov 15 04:33:04 ip-172-31-44-219 sudo[12972]: pam_unix(sudo:session): session opened for user root by ubuntu(uid=0)
Nov 15 04:33:04 ip-172-31-44-219 systemd[1]: Reloading myproj celery worker.
-- Subject: Unit myproj-celery.service has begun reloading its configuration
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit myproj-celery.service has begun reloading its configuration
Nov 15 04:33:07 ip-172-31-44-219 sh[12979]: celery multi v4.1.0 (latentcall)
Nov 15 04:33:07 ip-172-31-44-219 sh[12979]: > Stopping nodes...
Nov 15 04:33:07 ip-172-31-44-219 sh[12979]: > worker1@ip-172-31-44-219: TERM -> 12962
Nov 15 04:33:07 ip-172-31-44-219 sh[12979]: > Waiting for 1 node -> 12962.....
Nov 15 04:33:07 ip-172-31-44-219 sh[12979]: > worker1@ip-172-31-44-219: OK
Nov 15 04:33:07 ip-172-31-44-219 sh[12979]: > Restarting node worker1@ip-172-31-44-219: OK
Nov 15 04:33:07 ip-172-31-44-219 sh[12979]: > Waiting for 1 node -> None...
Nov 15 04:33:07 ip-172-31-44-219 sh[12992]: celery multi v4.1.0 (latentcall)
Nov 15 04:33:07 ip-172-31-44-219 sh[12992]: > worker1@ip-172-31-44-219: DOWN
Nov 15 04:33:07 ip-172-31-44-219 systemd[1]: Reloaded myproj celery worker.
-- Subject: Unit myproj-celery.service has finished reloading its configuration
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit myproj-celery.service has finished reloading its configuration
--
-- The result is done.
Nov 15 04:33:07 ip-172-31-44-219 sudo[12972]: pam_unix(sudo:session): session closed for user root
Perhaps CELERYD_PID_FILE="/var/run/celery/%N.pid" being unknown is the problem? Meaning, we cannot tell Systemd (via PIDFile=) what the actual location of the PID file is, because it's generated by celery itself, no?
The text was updated successfully, but these errors were encountered:
Checklist
master
branch of Celery.celery -A proj report
in the issue:Steps to reproduce
On Ubuntu 16.04.
sudo service <your-celery-service-name> start
sudo service <your-celery-service-name> reload
Expected behavior
Celery should gracefully reload.
Actual behavior
Celery does not gracefully reload. It shuts down, but never restarts.
After issuing the reload request (and subsequent failure to start), the output of
sudo journalctl -xe
doesn't seem to show anything nefarious:Perhaps
CELERYD_PID_FILE="/var/run/celery/%N.pid"
being unknown is the problem? Meaning, we cannot tell Systemd (viaPIDFile=
) what the actual location of the PID file is, because it's generated by celery itself, no?The text was updated successfully, but these errors were encountered: