MongoDB 6.0 crushes always - CENTOS

[Tarun_Gaur]

Hello @Mina_Ezeet ,

Welcome to The MongoDB Community Forums!

@Mina_Ezeet

"ctx":"SignalHandler","msg":"Received signal","attr":{"signal":15,"error":"Terminated"}}

Signal 15 also known as SIGTERM is sent to terminate a program, and is relatively normal behaviour. Please go through below thread as this is discussed in detail there.

Mongodb Receiving Signal 15 and Restarting

Hi, my mongodb is continuously getting shutdown, and restarting automatically. While going through the logs only thing which I came across was that it received signal 15 and got terminated. I am not sure of the root cause. If there is something which I am missing please do let me know. Below are the logs… "t":{"$date":"2022-12-24T23:10:01.743+00:00"},"s":"I", "c":"CONTROL", "id":20698, "ctx":"-","msg":"***** SERVER RESTARTED *****"} {"t":{"$date":"2022-12-24T23:10:01.743+00:00"},"s":"I", "…

@Mina_Ezeet

I think there are an issue realted to the ram usage and the wiredTiger engine.

So I think to reduce the cache size from 7 GB to 3 GB but What will happen if the cache usage become 3GB ? will mongod crash or it will try to free some cache ?

It’s important to note that changing the cache size may not necessarily solve the underlying issue. (which is something is sending MongoDB a Terminate signal). You may want to investigate further to determine why the service cannot stay up and address that root cause directly.

Additionally, you may want to consider tuning other MongoDB configuration options to optimize performance and memory usage based on your specific workload and available resources.

Apart from disk space issue, you can also take a look at your hardware resources to make sure your server is able to handle the load and is not getting overwhelmed. You can also check the MongoDB logs to see if there are any error messages or warnings that can provide more information about the cause of the crashes.

Regards,
Tarun