MongoDB service crashing
Project ID: 2c41e4bd-c910-4316-8e83-f0c3b6c63eab
My MongoDB started crashing yesterday out of the blue.
It seems that the process starts up, but then I get a "Writing fatal message" at the end of the logs.
Appreciate your help.
Solution:Jump to solution
then it's very likely you've hit the 512mb disk limit and mongo is now crashing because it has no more space during allocations, you would need to upgrade to hobby to get access to 5gb volumes, then go into the volume's settings to grow it to 5gb
10 Replies
Project ID:
2c41e4bd-c910-4316-8e83-f0c3b6c63eabThe logs show this message right before the crash:
"Unclean full-time diagnostic data capture shutdown detected, found interim file, some metrics may have been lost"
are you on the trial plan?
Yes
Solution
then it's very likely you've hit the 512mb disk limit and mongo is now crashing because it has no more space during allocations, you would need to upgrade to hobby to get access to 5gb volumes, then go into the volume's settings to grow it to 5gb
I see. Any way to check if I've hit that disk limit?
click the volume on the mongo database to view the disk usage, but keep in mind the current usage may not be at the upper limit since mongo could be trying to allocate more than 512mb and fail when only actually using maybe 200mb
Does the app size also count towards this limit? I have pretty much no data in my DB
A few records only
totally possible for that cause mongodb to ask for more than 512mb of disk
Got it. Thanks