10 months ago
Hi team! Thank you for great product and for free Trial version!
My MongoDB was running OK for number of days, and today with no clear reason it started to crash.
Here is logs:
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 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. 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 /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 [View Deploy details](https://railway.com/project/ca3b3b53-4db0-41d8-928f-c7662b59fb4c/service/ae999152-7df4-482d-8658-27995aebc2a1?id=f0742db4-9aac-4bbc-9448-c0a1367cffd9) > ⓘ Deployment information is only viewable by project members and Railway employees.
5 Replies
10 months ago
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 settings to grow it to 5GB.
brody
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 settings to grow it to 5GB.
10 months ago
It was running for at least 5 days with 500 MB volume limit. How can I debug why it started to crash only today?
Also according to the dashboard I'm using less than 500MB total.(Thought I am happy to get Hobby plan and I really like the platform so far, just want to understand why its started crashing only now)
Attachments
10 months ago
Mongo may be using a physical 196MB but it's now attempting to allocate more than 500MB and in doing so, it crashes.
brody
Mongo may be using a physical 196MB but it's now attempting to allocate more than 500MB and in doing so, it crashes.
10 months ago
I see, thank you for quick responses!
Status changed to Solved brody • 10 months ago