Mongo DB crashing

konstant880

PROOP

7 months ago

Hello, the mongoDB instance is crashing suddenly?

i have no idea why. Seems to indicate a memory error? the plan we're on should be sufficient for what we're doing now

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/ac6426dd-a18c-4117-984f-f72bb8d29f40/vol_lopk6ythde49ddus

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

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 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

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

BACKTRACE

Frame

Solved

3 Replies

echohack

EMPLOYEE

7 months ago

Looks like MongoDB can't start because there's not enough space on your Volume. Have you tried growing the size of the volume?

Status changed to Awaiting User Response Railway • 7 months ago

konstant880

PROOP

7 months ago

That's very strange? there is very little data on this database for now. Why would it do this? this must not happen in production later

Status changed to Awaiting Railway Response Railway • 7 months ago

echohack

EMPLOYEE

7 months ago

Looks like your volume was limited to 500MB. Unfortunately, MongoDB does not happily run with only 500MB of storage.

Since you're on the Pro plan, go into the volume settings to grow it to 5GB.

Status changed to Awaiting User Response Railway • 7 months ago

Status changed to Solved konstant880 • 7 months ago