3 months ago
Hi i am getting this error SIGKILL
Looks like you guys havent increased RAM even after upgrading to 20$ plan. fix this asap.
5 Replies
3 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
3 months ago
Your container was correctly set to 32GB of RAM, which matches the Pro plan's maximum per-service limit. The SIGKILL error you're seeing is because your application exceeds the 32GB memory limit. If your workload exceeds 32GB, you'll need to optimize your application's memory usage or split it across multiple services or replicas.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
how do i do that?
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Optimizing memory usage or splitting workloads across services falls under application-level architecture, which is outside Railway's support scope.
This would depend on your specific application and tech stack, so I'd recommend researching memory optimization techniques for whatever framework or language you're using.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 3 months ago
3 months ago
These workers are running fine on my local machine which is at 16GM ram , but failing at your end. moving out of railway. Thanks