[SERVER-50880] Mongod Server Failed with signal 6 Created: 11/Sep/20 Updated: 27/Oct/23 Resolved: 20/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 4.4.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Anandesh Sharma | Assignee: | Dmitry Agranat |
| Resolution: | Community Answered | Votes: | 0 |
| Labels: | KP44, SWCW | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Let me first explain the scenario first! I've installed mongo 3.6 and it was running fine but then I decided to upgrade, so I just took the backup using mongo tools. I removed and purged all the mongo packages and reinstalled the latest version. Restored the backup edited few changes in unit file and conf file.
I was running two mongo instances, copied everything separately (I'm sure, I did this perfectly) as it was the same when mongo 3.6 was running. Now, sometimes my mongod instance is killed:
I've looked into the mongo logs as well but I was unable to understand what is the exact reason also I've looked at other Jira threads which says maybe this is an issue of MEMLOCK limits, I've corrected that still, the problem persists.
I want urgent help please! If anyone wants additional information then I'm ready to provide ASAP. Thanks |
| Comments |
| Comment by Dmitry Agranat [ 20/Jan/21 ] | |||||||||||||||||||||||||||||||||
|
Hi anandeshsharma@gmail.com, I will go ahead and close this case as the issue was fixed in 4.4.3. Please reopen this case if you still experience the same issue after upgrading to 4.4.3. Regards, | |||||||||||||||||||||||||||||||||
| Comment by Dmitry Agranat [ 07/Jan/21 ] | |||||||||||||||||||||||||||||||||
|
We've made some work in 4.4.3 trying to fix this issue. Would be possible for you to try 4.4.3 and provide us with feedback? Thanks, | |||||||||||||||||||||||||||||||||
| Comment by Dmitry Agranat [ 12/Oct/20 ] | |||||||||||||||||||||||||||||||||
|
Were you able to set the locked-in-memory size to unlimited? Also, the team has built custom binaries for MongoDB Community build for Ubuntu 20.04 x86_64 with additional logging. The downloadable are here (public link). This should not have any impact on the application, and will only print additional information in the event the same bug causes the server to crash. Thanks, | |||||||||||||||||||||||||||||||||
| Comment by Dmitry Agranat [ 05/Oct/20 ] | |||||||||||||||||||||||||||||||||
|
Hi anandeshsharma@gmail.com, have you managed to set the locked-in-memory size to unlimited? If yes, did the reported issue occur again? | |||||||||||||||||||||||||||||||||
| Comment by Dmitry Agranat [ 24/Sep/20 ] | |||||||||||||||||||||||||||||||||
|
Hi anandeshsharma@gmail.com, yes, you will need to set your locked-in-memory size to unlimited. Can you also compress and attach into the same uploader link an archive of all of /var/log/messages*, /var/log/syslog* and {{ /var/log/dmesg*}}? Thanks, | |||||||||||||||||||||||||||||||||
| Comment by Anandesh Sharma [ 18/Sep/20 ] | |||||||||||||||||||||||||||||||||
|
Yeah, I've uploaded it as, mongod.tar.gz & diagnostic.tar.gz UNIX ulimits (hard)
| |||||||||||||||||||||||||||||||||
| Comment by Dmitry Agranat [ 13/Sep/20 ] | |||||||||||||||||||||||||||||||||
|
Would you please archive (tar or zip) the full mongod.log files and the $dbpath/diagnostic.data directory (the contents are described here) and upload them to this support uploader location? Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. Also, please post the MEMLOCK limit after you have corrected it? Thanks, |