10 months ago
My project is facing some errors in logs.
MongoDB connected
🚀 Server running on port 8080
Health check endpoint hit
Stopping Container
npm error path /app
npm error command failed
npm error signal SIGTERM
npm error command sh -c node server.js
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-08-15T05_11_26_252Z-debug-0.log
🟢 Client connected: YEWLQBb_KESD8rW8AAAD
5 Replies
10 months ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 npm start error
- 🧵 Having SIGTERM issue in Node.js + Express project
- 🧵 Node.js App gets SIGTERM after successful start and healthcheck
If you find the answer from one of these, please let us know by solving the thread!
10 months ago
Provide the snippet of the server file, which has the healthcheckup endpoint
10 months ago
Ensure that you have configured the health check endpoint correctly. You can refer to my post, in which I have mentioned everything about health checkups
https://station.railway.com/questions/node-js-service-failing-to-deploy-with-s-dc58e402#mk2w
clashing
Ensure that you have configured the health check endpoint correctly. You can refer to my post, in which I have mentioned everything about health checkups <https://station.railway.com/questions/node-js-service-failing-to-deploy-with-s-dc58e402#mk2w>
10 months ago
Any progress, anup2702?
If the previous reply helped, do mark that as the solution
10 months ago
Hey, the "Stopping Container" and SIGTERM logs that appear after a new deployment refer to the termination of the previous deployment's container, not the new one. You latest deployment is probably fine. Railway will probably make this distinction clearer in the logs at some point...