Can you help us debug why our "Application Failed to respond"
We run a nestjs - postgres app on railway. Since last week or so the app has been shutting down with auto restart happing too late for almost every day.
We do not know the reason. We have been running railway for more than a year and this did not happen.
I think there is a memory usage issue but looking at the logs I do not see any useful information. No error logs.
See the screenshot, just in the last hour these were the times when the app was offline.
If we could Identify what in our app is causing this we could resolve this but we are just stuck now and poking with try catch here and there.
Have been using railway for a long time. Would really appreciate if you guys can help us or point us to the logs which is causing the app to fail
Project id is: 6d0f799e-be59-4388-899d-f00456f30667
6 Replies
Project ID:
6d0f799e-be59-4388-899d-f00456f30667I've faced similar issues with one of my apps, the app would run fine for a while, then suddenly stop while still reading as active from railways side of things and a redeploy or restart would fix it, I thought I had pretty good error handling but there were no errors, I was scratching my head for days, eventually I sat down and added a crap ton of verbose debug logging (structured json) to nearly every little part of the code and finally figured out the issue (code issue).
With all that said, my point is that railway will not have any better observability into what your app's code is doing (or not doing) than you would, if you don't know why it's stopped, they aren't going to either.
Got it @Brody Thank you
I'm sorry I don't have the answer you want, but unfortunately it's not that simple in this situation
100% agree. Railway has done an amazing job with the logs. But its just so annoying I couldn't figure this out
I feel you, it's really frustrating when these kinds of issues happen and you don't immediately know why