Worker (pid:233) was sent SIGKILL! Perhaps out of memory?
[CRITICAL] WORKER TIMEOUT (pid:233)
42 Replies
Project ID:
N/AN/A
I see that you're on hobby now, where you on hobby when you got this error?
yes im in hobby, but i upgraded my plan already to pro
i'm having this error
what do your memory metrics look like?
and when you upgraded to pro, did you move your project over to your pro account?
it looks like this
yes i moved it to pro account alreadyy
have you redeployed the project since
yes i redeployed it already
then you aren't running out of memory and that means there is a code issue here
how long should a single http request take to your app?
about 5 seconds
there's an issue with your code, it's blocking the requests from finishing and causing issues, my recommendation would be to add debug logging, better error handling and telemetry data so that you can more easily debug your code
can i dm you? and send you my git repository
i think im having a problem in gunicorn code
no sorry, this isn't an issue with Railway
please follow my recommendation, without those things it would be very hard for you to debug
this is my railway.yml
build:
start:
name: python-start
run: gunicorn -c gunicorn_config.py -b 0.0.0.0:$PORT -t 600 your_main:app
railway does not have support for yaml
what should i do instead?
and if it did, that would not be the correct syntax
a Procfile
i think that is our problem
should i change it to procfile?
yes, that's one of the simplest ways to set a start command
what should i put in start command
sorry it was my first time deploying in railway
use the command you sent above
actually nevermind, forget a Procfile, set the start command in the service settings
okay im gonna set it
it shows this
Error: No application module specified.
your start command is incorrect, please review gunicorns documentation
i changed it to this
gunicorn -c gunicorn_config.py main:app
and this is my gunicorn_config.py
gunicorn_config.py
bind = "0.0.0.0:$PORT"
workers = 4
timeout = 120
without reading the documentation myself I wouldn't be able to tell you if that's valid or not
can't hurt to try
bro what port should i use?
should i follow the documentation $PORT or set it to 8000 instead
gunicorn binds to 0.0.0.0:$PORT by default actually, so you can omit that
should i remove the bind = "0.0.0.0:$PORT"
yes, it's redundant
thaaank youu so muchhh!! i will try it
bro theres no error like critical error out of memory
this is my new error now
unfortunately a start command change didn't solve anything
please follow my recommendations
thank you i will do that!!
hiii brody thank you so muchh man!!!
what was the problem?
the main problem is the railway.yml and removing the bind and port in gunicorn_config.py, now we are able to connect our app in railway
awesome
awesomee man!! thank you so muchh!!
you helped us a lot
Solution
lesson of the day, don't get chat gpt to write you railway config
yeaah HAHAHAHA i learned my lesson!!!