app killed with exit code 137
Anonymous
TRIALOP

2 years ago

Hi, my project(id: ffc699a7-8a82-4231-949c-107a6fecfffc) was killed. However, it seems the memory, cpu and timeout didn't exceed the limit of my plan(hobby). could you please help me figure out the potential issue? Appreciate your help

Killed

error Command failed with exit code 137.

3 Replies

brody
EMPLOYEE

2 years ago

what kind of app are you running?


Anonymous
TRIALOP

2 years ago

Zero knowledge prover, it is computation intense


brody
EMPLOYEE

2 years ago

what do the metrics look like during the crash?


Anonymous
TRIALOP

2 years ago

CPU: 0.3 vCPU
Memory: 200MB
Network: 45MB


brody
EMPLOYEE

2 years ago

very good possibility that there was a resource spike that went above your plan limits, a spike fast enough that it wasn't caught by the metrics recording frequency


Anonymous
TRIALOP

2 years ago

I’m in hobby plans, I can run it on my laptop with 8GB ram. Not sure why it will exceed the limit. It’s so hard to debug


Anonymous
TRIALOP

2 years ago

It’s killed after30 seconds even if I upgrade to pro plan. Is it the issue from timeout?


Anonymous
TRIALOP

2 years ago

Ahhh it pass now. You are right! The spike of memory is 9GB exceeding my hobby plan limit. Appreciate your help 🙏🙏🙏


brody
EMPLOYEE

2 years ago

there really should be better feedback from the railway side of things, like a popup saying this service exceeded it's memory/cpu and was shut down kinda thing


phact
TRIAL

2 years ago

Does yours actually say exit code 137? Mine just says Killed and I'm stuck wondering if it's OOM or something else.


brody
EMPLOYEE

2 years ago

theirs did say the exit code, but I have seen many help threads with just "killed" that were still OOM.


phact
TRIAL

2 years ago

yeah mine was the latter but I did manage to get a 137 out of it with echo $?


Loading...