10 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?
Attachments
1 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 Node.js App gets SIGTERM after successful start and healthcheck
- 🧵 Node.js Service Failing to Deploy with SIGTERM Error (Health Check Timeout)
- 🧵 MongoDB Service Connected but App Cannot Establish Database Connection - Mongoose State 0 (Disconnected)
- 🧵 Service Times Out on Outbound API Calls (504 Error)
If you find the answer from one of these, please let us know by solving the thread!
10 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 • 10 months ago