0

So currently I am hosting a MEAN stack project on Linode cloud. Every few days the Mongodb side of my project seems to crash and the only way I can fix it is by logging into the project via WinSCP, deleting the mongod.log file and then rebooting the project. This is however only a short-term solution.

So far I’ve changed the rotation of the log file from weekly to daily, in order to reduce the size of the log file, however that hasn’t worked.

So in the last crash it gave the message:

FileStreamFailed: Failed to write to interim file buffer for full-time diagnostic data capture: /var/lib/mongodb/diagnostic.data/metrics.interim.temp\nActual exception type: mongo::error_details::ExceptionForImpl<(mongo::ErrorCodes::Error)39, mongo::AssertionException>\n"
Improve this question
5
  • What do the logs, either mongod or from the OS, say about the process terminating? We can only guess right now as no troubleshooting information has been provided in the question Commented Nov 24, 2022 at 15:08
  • So I read through my log file. One of them gave the message: "FileStreamFailed: Failed to write to interim file buffer for full-time diagnostic data capture: /var/lib/mongodb/diagnostic.data/metrics.interim.temp\nActual exception type: mongo::error_details::ExceptionForImpl<(mongo::ErrorCodes::Error)39, mongo::AssertionException>\n"}}" Commented Nov 28, 2022 at 7:55
  • Google suggests that error is related to your disk being full reference. This would also match the stated behavior that deleting a log file allows you to restart the database. Perhaps you should look at clearing some more space on disk or moving the database elsewhere? Commented Nov 28, 2022 at 14:17
  • So I tried your recommendation. It didn't really make any better. In fact right now the server has totally crashes seconds after I rebooted it Commented Nov 30, 2022 at 6:09
  • I'm not sure how we are supposed to help without more information about the current situation or problem. Everything you've shared up to this point has suggested that the disk/directory that the database is using is full. If that's still the case (how big is the database, how much space is on the disk, etc) then that problem still needs to be addressed. If there is a different problem now then we'd those new details to advise differently. Also, log rotation often doesn't automatically delete the files, it just creates a new one but leaves the old one in place. Commented Nov 30, 2022 at 13:47
Related questions
6
Mongodb crashing all the time
9
How can I find out why mongodb crashes?
7
MongoDB log file
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.