[SOLVED] Celery exiting unexpectedly | Railway | Page 1

celest iron Sep 19, 2022, 4:01 PM

#

I have a worker service which is running celery for my Django app. Shortly after starting up it seems to be exiting for some reason.

[2022-09-19 15:44:59,287: ERROR/MainProcess] Process 'ForkPoolWorker-95' pid:103 exited with 'signal 9 (SIGKILL)'

You're all probably getting tired of hearing this, but this was all working on Heroku. Let me know what additional information would be helpful. Thanks!

project ID: 1e39500f-9b84-42bc-9b23-0972f4584570

#

One difference that I notice in the logs from the ones in Heroku is that Heroku is showing concurency set to 8. Railway is showing 96. This isn't something that I'm currently controlling with any settings on either platform.

Heroku: - *** --- * --- .> concurrency: 8 (prefork)
Railway:- *** --- * --- .> concurrency: 96 (prefork)

celest iron Sep 19, 2022, 5:46 PM

#

Going to try setting my concurrency to 1 with --concurrency=1, but I got kicked out and can't log into my dashboard right now

celest iron Sep 19, 2022, 9:30 PM

#

Looks like explicitly setting the concurrency when launching celery has resolved this issue. Ex.

exec celery -A app.tasks.celery_app worker --concurrency=2 -l INFO --beat -l INFO

#

[SOLVED] Celery exiting unexpectedly

#[SOLVED] Celery exiting unexpectedly