R
Railway11mo ago
lahav.

ERROR MONGODB

Hello, I have this error on MongoDB :
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 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
Connection accepted
client metadata
Connection accepted
client metadata
Auth metrics report
Successfully authenticated
Received first command on ingress connection since session start or auth handshake
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
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 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
Connection accepted
client metadata
Connection accepted
client metadata
Auth metrics report
Successfully authenticated
Received first command on ingress connection since session start or auth handshake
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
Solution:
okay nothing wrong with the memory usage, but looks like your disk is a bit too full, you will have to upgrade to hobby for a 5gb volume, then you can grow the current volume to 5gb and restart mongo
Jump to solution
13 Replies
Percy
Percy11mo ago
Project ID: N/A
Brody
Brody11mo ago
can you send a screenshot of your memory metrics please
lahav.
lahav.OP11mo ago
No description
Brody
Brody11mo ago
set to 6hr?
lahav.
lahav.OP11mo ago
No description
Solution
Brody
Brody11mo ago
okay nothing wrong with the memory usage, but looks like your disk is a bit too full, you will have to upgrade to hobby for a 5gb volume, then you can grow the current volume to 5gb and restart mongo
lahav.
lahav.OP11mo ago
Alright will do that now, thanks for your help man How can I grow the current volume ? (I subscribed to Hobby plan)
Brody
Brody11mo ago
from within the volumes settings, its not obvious i know thats why this feedback exists https://discord.com/channels/713503345364697088/1191507681282895903
lahav.
lahav.OP11mo ago
No description
lahav.
lahav.OP11mo ago
that's this ?
Brody
Brody11mo ago
yep just click the grow button! then go and restart the mongo service if it doesnt restart it automatically
lahav.
lahav.OP11mo ago
Excellent !! Thanks a lot All is working good
Brody
Brody11mo ago
awsome!
Want results from more Discord servers?
Add your server