a year ago
npm error path /app
npm error command failed
npm error signal SIGTERM
npm error command sh -c node index.js
Connection accepted
client metadata
WiredTiger message
basic node, mongo, redis deployment. works perfectly locally, but getting this error every time in the build logs, though build seems to continue. redis and mongo connect correctly.
have seen this error discussed quite a bit in the forums, which suggests this is a railway concern. any guidance on this?
2 Replies
Status changed to In Progress parmstar • about 1 year ago
a year ago
Hi,
The issue is that npm is not passing SIGTERM correctly to the node process that is running your app, this is only going to happen on the old deploys though.
Adjust the start command in the service settings to run your
.js file with node directly.
Status changed to Solved angelo-railway • about 1 year ago