[SERVER-20932] Debian 8.1 mongo 3.0.6 killed by oom killer Created: 15/Oct/15  Updated: 28/Apr/16  Resolved: 15/Oct/15

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 3.0.6
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: marco berri Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File messages.log    
Operating System: ALL
Participants:

 Description   

Mongo 3.0.6 crash without message on log.
debian 8.1

se log attach



 Comments   
Comment by Ramon Fernandez Marina [ 15/Oct/15 ]

marcoberri@gmail.com, as explained in the log you sent the mongod process was killed by the operating system's OOM killer.

Oct 15 02:00:33 vm4553 kernel: [723954.577468] Out of memory: Kill process 18100 (mongod) score 368 or sacrifice child

This can happens when there's not enough memory for mongod to work as configured, so I'd recommend you revisit your memory configuration and provide sufficient memory for mongod to operate.

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Generated at Thu Feb 08 03:55:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.