mongodb deployment crashed
darksideevil
TRIALOP

2 years ago

i didn't enter my app for two days, then when i entered i'm getting this err on my console:

connection to 35.212.138.205:52417 closed

so reviewed my deployments on my project it's crashed and logs:

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

Initialized wire specification

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

Frame

Frame

Frame

View Deploy details

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

1 Replies

brody
EMPLOYEE

2 years ago

Your database has likely crashed because of the limited disk space of 500MB, you would need to upgrade to the Hobby plan to access 5GB disks, once on the Hobby plan you can go into your volume's settings to grow it to 5GB.


Loading...