a year ago
Hello, I have MongoDB in a "Crashed" state. I tried restarting it, but it doesn't come back up properly, and the last thing the deploy log says is:
container event container died
--->
[Nest] 15 - 10/14/2024, 10:13:55 PM
ERROR [ExceptionsHandler] connection to 35.212.144.195:44085 timed out;
"I don't recognize that host 35.212.144"
MongoServerSelectionError: connection to 35.212.144.195:44085 timed out.
The deploy logs show that it does this several times, getting stuck in a loop but not moving forward.
Connection accepted
Client metadata
Auth metrics report
Successfully authenticated
Received first command on ingress connection since session start or auth handshake
Connection ended
Connection ended
Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost
Writing fatal message
Writing fatal message
Writing fatal message
BACKTRACE
Frame….
This is the full deploy log:
Flow Control is enabled on this deployment
Initializing full-time diagnostic data capture
Setting new configuration state
Timestamp monitor starting
Listening on
Listening on
Listening on
Waiting for connections
mongod startup complete
Connection accepted
client metadata
Connection accepted
client metadata
Connection accepted
client metadata
Connection accepted
client metadata
Connection accepted
client metadata
Auth metrics report
Auth metrics report
Successfully authenticated
Successfully authenticated
Received first command on ingress connection since session start or auth handshake
Received first command on ingress connection since session start or auth handshake
Connection ended
Connection ended
Connection ended
Connection ended
Connection accepted
client metadata
Auth metrics report
Successfully authenticated
Received first command on ingress connection since session start or auth handshake
Connection ended
Connection ended
Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost
Writing fatal message
Writing fatal message
Writing fatal message
BACKTRACE
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
container event container died
What can I do to get MongoDB working again?
> ⓘ Deployment information is only viewable by project members and Railway employees.
1 Replies
a year ago
You're on the trial plan and are limited to 500MB Volumes, MongoDB can not happily run with only 500MB, you will need to upgrade to the Hobby plan for access to 5GB volumes, after the upgrade, go into the volumes settings to grow it to 5GB.