6 months ago
MongoDB ran out of volume, which is when I upgraded the volume size to 20GB, and as soon as I tried to start the database, it started crashing immediately. This is probably because of some file corruption. Any ways to fix this on the railway since there's no way to SSH?
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/5b1827b2-c9cc-4562-9c5a-9f78c15e1a3a/vol_a2po2kgue1ixv61k
Starting Container
MongoDB starting
Applied --setParameter options
Memory available to mongo process is less than total system memory
Initialized wire specification
Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
Build Info
Operating System
Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueueSize.
Successfully registered PrimaryOnlyService
Options set by command line
Successfully registered PrimaryOnlyService
Storage engine to use detected by data files
Multi threading initialized
Using the XFS filesystem is strongly recommended with the WiredTiger storage engine. See http://dochub.mongodb.org/core/prodnotes-filesystem
Starting TenantMigrationAccessBlockerRegistry
Opening WiredTiger
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
WiredTiger error message
Fatal assertion
***aborting after fassert() failure
Writing fatal message
Writing fatal message
Frame
BACKTRACE
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
Frame
3 Replies
6 months ago
You should be able to:
Set start command
sleep infinitySSH into the box and run the mongo script to drop the WAL (I think it's mongod --repair --dbpath /var/lib/mongodb but you might have to poke around and check)
Remove the
sleep infinitystartup command
Status changed to Awaiting User Response Railway • 6 months ago
6 months ago
Thank you! Didn't know about railway ssh - did the trick :)
Status changed to Awaiting Railway Response Railway • 6 months ago
Status changed to Solved Anonymous • 6 months ago