There was a problem loading the comments.

Mongod OOM Killer error

Support Portal  »  Knowledgebase  »  Viewing Article

  Print

Original Question

or Issue:

Mongod crashing with OOM Killer error:
1667a5b2b58de386edb98edd86ed32f2e803a9ef55e4e69e17e9ea22a10e4251b503e25843e22977?t=eecb9dcffe4fc0f76c9e52ad0c57f2b3

Environment:

  • Product - FileCloud Server (mongod)
  • Version -  Any
  • Platform - Any
Steps to Reproduce:

 

 

Error or Log Message:  

Defect or

Enhancement Number:

 
Cause:  

Resolution or

Workaround:

 Change the system priority for which service to kill when memory is usage is high:

systemctl edit mongod
[Service]
OOMScoreAdjust=-999

systemctl restart mongod

 

The value can range from anywhere between -1000 and 1000, the lower the number, the less likely the OOM killer will stop this service.

c3bbe7497250b3629a033fcbcf805591647d9b51581badb1951bbedcbd824892e7f97ca286a71058?t=946732da661e6ce84521363576c56cc3

Notes:   

Share via

Related Articles


Self-Hosted Help Desk Software by SupportPal
© FileCloud