Hi,
On 07/27/2016 08:02 AM, Roberto De Ioris wrote:
Hi,
I have an issue using uwsgi and celery. When celery is stopped by uwsgi,
it tries to kill one of its pool subprocess but it fails because this
subprocess doesn't exist anymore (as if uwsgi would have done the job
already). I posted some more information here:
http://stackoverflow.com/questions/38521586/billiard-writes-errno-3-no-such-proces-when-uwsgi-shuts-celery-down
Hi, probably the easiest thing to do is setting celery as a 'true daemon'
so it will detach completely from uwsgi. Check --attach-daemon2 option for
the daemonize flag
Thanks! I'm not willing to use the daemonize flag but I should be able
to do something with the stop_signal parameter of attach-daemon2. If the
celery pool processes are directly shot by uwsgi, it is not so simple as
setting the stop signal to what celery worker expects, I would need to
send a different signal to the worker and the pool processes. But I can
in the worst case send something that will be handled manually on the
celery side. If you see a better solution thanks to let me know :)
Adrien Cossa
Entwicklung
init.at informationstechnologie GmbH
Fockygasse 29-31 | 4.OG | 1120 Wien
Mail: [email protected]
Tel: +43 1 522 53 77 39
Fax: +43 1 522 53 77 55
Web: http://www.init.at
Diese Nachricht ist vertraulich und nur für den Adressaten bestimmt. Sollten
Sie kein autorisierter Empfänger sein, ist jede Offenlegung, Weiterleitung
oder sonstige Verwendung dieser Nachricht nicht
gestattet. Bitte informieren Sie in diesem Fall den Absender und löschen Sie
alle Kopien - vielen Dank.
This message is confidential and only intended for its recipient. If you are
not the intended recipient, any disclosure, distribution or any other use of
this mail is prohibited. In this case, please notify the
sender and delete all copies of the message - thank you.
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
