I upgraded to the hobby plan thinking it was a resource issue, but the problem persists. I'm working on a brand new project so my db doesn't even have much in it. However, the instance keeps crashing and I have to keep restarting it. Here are the logs:

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

Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/2db62f35-924e-4338-81c0-eb084ae9cf11/vol_vcpg5jrac0meewdm

container event container died

WiredTiger opened

WiredTiger recoveryTimestamp

/sys/kernel/mm/transparent_hugepage/enabled is 'always'. We suggest setting it to 'never' in this binary version

vm.maxmapcount is too low

Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'

Updated wire specification

Initialized wire specification

current featureCompatibilityVersion value

Clearing temp directory

Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize.

Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost

Initializing cluster server parameters from disk

Writing fatal message

Successfully registered PrimaryOnlyService

Flow Control is enabled on this deployment

Writing fatal message

Successfully registered PrimaryOnlyService

Writing fatal message

Initializing full-time diagnostic data capture

Multi threading initialized

Setting new configuration state

Starting TenantMigrationAccessBlockerRegistry

Timestamp monitor starting

MongoDB starting

Listening on

Memory available to mongo process is less than total system memory

Listening on

Listening on

Build Info

Waiting for connections

Operating System

Options set by command line

Detected unclean shutdown - Lock file is not empty

BACKTRACE

mongod startup complete

Frame

Storage engine to use detected by data files

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.