a year ago
My Mongo Instance is getting crashed
Build Info
Operating System
Options set by command line
Detected unclean shutdown - Lock file is not empty
Storage engine to use detected by data files
Recovering data from the last clean checkpoint.
Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
WiredTiger message
WiredTiger message
WiredTiger message
WiredTiger message
WiredTiger message
WiredTiger message
WiredTiger message
WiredTiger message
WiredTiger message
WiredTiger message
WiredTiger message
WiredTiger message
WiredTiger opened
WiredTiger recoveryTimestamp
For customers running MongoDB 7.0, we suggest changing the contents of the following sysfsFile
vm.max_map_count is too low
Updated wire specification
current featureCompatibilityVersion value
Clearing temp directory
Initializing cluster server parameters from disk
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
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
2 Replies
a year ago
Hello,
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 volume settings to grow it to 5GB.
Best,
Brody
Status changed to Awaiting User Response Railway • 11 months ago
Status changed to Solved brody • 11 months ago
a year ago
Thanx
Status changed to Awaiting Railway Response Railway • 11 months ago
Status changed to Solved sourcecatch-konnect • 11 months ago