a year ago
The Mongo DB crashed by itself for no reason, i need the data contained in the disk please. What can i do?
ⓘ Deployment information is only viewable by project members and Railway employees.
6 Replies
a year ago
I've been experiencing the same problem for some days now. Even when I restart, it crashes again a few seconds after. I am no longer able to access the LibreChat web URL possibly because of this even though everything had worked perfectly well for a week.
Status changed to Awaiting Railway Response railway[bot] • 11 months ago
a year ago
Ivory, you're on the trial plan and are limited to 500MB Volumes, MongoDB can not happily run with only 500MB, you will need to upgrade to the Hobby plan for access to 5GB volumes, after the upgrade go into the volume's settings to grow it to 5GB.
tosin, even though you're Pro, you may have not grown the volume after upgrading so you could also still only have a 500MB volume.
a year ago
I don't think that is a disk space problem.
...
Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost
...
a year ago
This is the complete log
Frame
Frame
Frame
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
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.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
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
a year ago
Those are not the complete logs, either way, please let me know if you continue to experience issues after growing the volume to 5GB.
a year ago
But I don't want to expand the volume; I just need to retrieve the data. Can I attach the volume to an Ubuntu machine to access it?