MongoDB instance crashing
jayde
HOBBYOP

2 years ago

I have a mongodb instance crashing, nothing stands out in the logs.
Anyone know anything?

Logs:

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' 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
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 tcpFastpenQueueSize.
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' in this binary version
vm.max_map_count is too low
Updated wire specification
curent 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

View Deploy details

ⓘ Deployment information is only viewable by Project members and Railway admins.

5 Replies

brody
EMPLOYEE

2 years ago

You're on a trial plan, meaning mongo would only have a 500MB volume and mongo is running out of space and crashing, you would need to upgrade to Hobby for access to 5GB volumes. Once you upgrade you can go into the volume's settings and grow it to 5GB.

jayde
HOBBYOP

2 years ago

You're on a trial plan, meaning mongo would only have a 500MB volume and mongo is running out of space and crashing, you would need to upgrade to Hobby for access to 5GB volumes. Once you upgrade you can go into the volume's settings and grow it to 5GB.

Thanks for the response!

jayde
HOBBYOP

2 years ago

@brody, do you know how I could grow the volume? I can't seem to access it since it is crashing.

brody
EMPLOYEE

2 years ago

Click on the volume, click on settings, click on grow.

jayde
HOBBYOP

2 years ago

Thanks, I didn't know the volume was clickable on the dashboard. Thank you!

Loading...