Our mongo services are down on all of our environments
regigeorge1
PROOP

a month ago

ALl mongo services on all of our envs are currently down.

error: The database deployment has stopped running.

log shows:

Shutting down the TTL monitor

Finished shutting down journal flusher thread

Shutting down checkpoint thread

Finished shutting down checkpoint thread

Timestamp monitor shutting down

Deregistering all the collections

WiredTigerKVEngine shutting down

Shutting down session sweeper thread

Finished shutting down session sweeper thread

Closing WiredTiger

WiredTiger message

WiredTiger message

WiredTiger message

Connection ended

WiredTiger closed

shutdown: removing fs lock...

Dropping the scope cache for shutdown

Shutting down full-time diagnostic data capture

Now exiting

mongod shutdown complete

Shutting down

Solved

6 Replies

regigeorge1
PROOP

a month ago

This is urgent. Unfortunately, our live env is down.


regigeorge1

This is urgent. Unfortunately, our live env is down.

kremalicious
PRO

a month ago

welcome to the club! I am waiting for an answer to my own thread for the last 3 hours so be prepared to wait. So far support tells everybody that in recent incident is resolved and restarting db services resolves everything, which for many people it does not


kremalicious

welcome to the club! I am waiting for an answer to my own thread for the last 3 hours so be prepared to wait. So far support tells everybody that in recent incident is resolved and restarting db services resolves everything, which for many people it does not

regigeorge1
PROOP

a month ago

Are you having issues with mongo services too?


regigeorge1

Are you having issues with mongo services too?

kremalicious
PRO

a month ago

yes, my thread is over here, and my logs look exactly like yours https://station.railway.com/questions/no-connection-to-database-shuts-down-af-daf851c8

You can also see that almost all new threads in discussion right now are about database connection issues


a month ago

Hello,

We had an incident earlier that caused some running workloads to be unexpectedly terminated while the status in the UI didn't properly update. This has since been resolved, but in some cases, you may need to redeploy your services.

You can find the post-mortem for the incident here: https://blog.railway.com/p/incident-report-february-11-2026

Our deepest apologies for the inconvenience this has caused.


Status changed to Awaiting User Response Railway 28 days ago


regigeorge1
PROOP

a month ago

Thank you @kremalicious and @brody. I was able to restart all services and all seems to be up now. Thank you for responses and direction.


Status changed to Awaiting Railway Response Railway 28 days ago


Status changed to Solved regigeorge1 28 days ago


Loading...