Multiple Gunicorn Workers lead to SIGKILL
sknat26
TRIALOP

a year ago

I am deploying a Flask app using gunicorn. In the start command when I set workers to more than 1, the app crashes. In the deploy logs, the workers get booted and immediately get shut down by SIGKILL.

Solved

5 Replies

brody
EMPLOYEE

a year ago

Hello,

You are very likely running out of memory, the trial plan is limited to 500MB, you would need to upgrade to a paid plan for more memory.

Best,

Brody

Status changed to Awaiting User Response Railway • about 1 year ago

sknat26
TRIALOP

a year ago

I see. Thank you for the reply. If I use one gunicorn worker, the app deploys fine. However, it shuts down with a similar SIGKILL error when my app uses the OpenAI whisper library for transcription. I checked the metrics, and the app doesn't exceed 500 mb during this activity. Could this be something else?

Status changed to Awaiting Railway Response Railway • about 1 year ago

brody
EMPLOYEE

a year ago

Check your activity log, does it say you went out of memory?

Status changed to Awaiting User Response Railway • about 1 year ago

sknat26
TRIALOP

a year ago

It says this: "[ERROR] Worker (pid:4) was sent SIGKILL! Perhaps out of memory?"

Status changed to Awaiting Railway Response Railway • about 1 year ago

brody
EMPLOYEE

a year ago

Please upgrade to Hobby and redeploy, you are running out of memory.

Status changed to Awaiting User Response Railway • about 1 year ago

Status changed to Solved brody • about 1 year ago

Loading...