Portfolio with node backend and mongodb for database

ananke85

HOBBYOP

2 years ago

Some days ago I've set up correctly my deployment of portfolio_back. Now the mongoDB is crashing and I didn't make any change on the repository to affect the deployment. When trying to connect the mongo in atlas I'm getting this message: read ECONNRESET. And in the deploy logs I'm getting these messages: 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

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

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.

Can you help me? I don't know where's the issue if the website was running correctly.

View Deploy details

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

1 Replies

brody

EMPLOYEE

2 years ago

It's very likely your mongo database has run out of storage, you will need to upgrade to Hobby and then you can go into the mongo data volume to grow the volume.