My MongoDB deployment is consistently crashing. It worked fine as I successfully inserted users into the DB previously through my backend. The code for connecting to the database has not been altered since then, and no operations were performed aside from searching the DB for the login functionality. These are the deployment logs which repeat with each redeployment attempt. Current used volume is ~192/500MB.

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

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

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

Frame

Frame

Frame

Frame

Frame

Frame

Frame

Frame

Frame

Frame

Frame

Frame

Any help would be greatly appreciated!

View Deploy details

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