Healthy, non-serverless service is being terminated after successful health check

hoyinboye
FREE

2 months ago

Hello,

My Node.js service is being shut down by a SIGTERM signal 2-3 seconds after it starts and successfully passes its health check.

I have logs confirming the server starts on the Railway-provided port, and a custom log message confirms the /healthz endpoint is being hit by the health check. Serverless mode is disabled.

Can you please investigate why a healthy, active deployment is being terminated?

$10 Bounty

1 Replies


2 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 about 2 months ago


Healthy, non-serverless service is being terminated after successful health check - Railway Help Station