a year ago
Looks like MongoDB crashed overnight, and now I cant start.
Getting this msg Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost.
I cant connect to cli, what can I do?
ⓘ Deployment information is only viewable by Project members and Railway admins.
5 Replies
a year ago
I am really not sure how to tell since I cant connect to it to see. I did start on the free plan, but switched to hobby. Started from a deploy on railway template. Here is my log
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 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
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
I am really not sure how to tell
Click on the volume, please answer my above questions.
a year ago
Thank you. I did not see it before. But clicking on the volume, then settings I saw size was set to 500mb. Clicked the grow option, and now everything is fine.
Status changed to Solved Railway • over 1 year ago