Mongo DB Crash
Successfully registered PrimaryOnlyService
Multi threading initialized
Starting TenantMigrationAccessBlockerRegistry
MongoDB starting
Memory available to mongo process is less than total system memory
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
Opening WiredTiger
WiredTiger opened
WiredTiger recoveryTimestamp
You are running on a NUMA machine. We suggest launching mongod like this to avoid performance problems: numactl --interleave=all mongod [other options]
/sys/kernel/mm/transparent_hugepage/enabled is 'always'. We suggest setting it to 'never'
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
MongoDB service crashes on start. Default config afaik. Log above.Solution:Jump to solution
I'd still upgrade to hobby asap, I have seen countless reports of instabilities from mongo on the trial plan due to the 500mb disk
14 Replies
Project ID:
668b188c-847c-46c1-a06d-91726695b300
668b188c-847c-46c1-a06d-91726695b300
is there data in the database?
negative
gunna delete service and retry from scratch
wont connect over public
but doesnt crash
and this is a completely new mongodb?
yeah
youre on trial plan right?
yeah
its very possible mongo needs more than 500mb of disk space
its showing public connection working now on the dashboard. still working out connecting thru my local termianl
and we're good...
Solution
I'd still upgrade to hobby asap, I have seen countless reports of instabilities from mongo on the trial plan due to the 500mb disk
ok