Deployment crashed for seemingly no reason
benzelcurry
HOBBYOP

2 years ago

I've had a web app hosted through Railway for nearly a year now, and yesterday it crashed despite no changes being made to any of the code. I went through the database and made sure nothing was submitted to it that could have resulted in something weird, but there have been no recent additions to it.

I'm not very well-versed in diagnosing issues through deployment logs, but this is what is being thrown when the error starts:

at Timeout._onTimeout (/app/node_modules/mongodb/lib/sdam/topology.js:277:38)

at listOnTimeout (node:internal/timers:569:17)

at process.processTimers (node:internal/timers:512:7) {

reason: TopologyDescription {

type: 'Unknown',

servers: Map(1) {

'containers-us-west-28.railway.app:7635' => [ServerDescription]

},

There's more, but hopefully this is sufficient for the time being. Like I said, I haven't made any adjustments to the code, so I'm not sure why this error would suddenly be throwing.

Any help would be appreciated. Thanks!

1 Replies

brody
EMPLOYEE

2 years ago

your code is still trying to connect to the deleted legacy database, you would have received countless emails about migrating your legacy database before it was shut down and deleted


Loading...