a year ago
My Mongo container was down and cannot be started and this was repeated in logs until it died. I was thinking it can be low space of volume, but volume shows only 190mb used from 500mb available. I fix it by using /data/db2 instead of /data/db it clean data but at least it was able to start, what can cause this problem?
Logs:
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/c5632c6d-e929-4509-a22a-3256b9bc5fc6/vol_pwq2qel9tqjyfkpe
Initialized wire specification
Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize.
Successfully registered PrimaryOnlyService
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 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
/sys/kernel/mm/transparent_hugepage/enabled is 'always'. We suggest setting it to 'never' in this binary version
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
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.