[SERVER-49684] Mlock error at mongo console opening - failed to mlock: Cannot allocate locked memory. Created: 17/Jul/20 Updated: 27/Oct/23 Resolved: 21/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vincent Liagre | Assignee: | Dmitry Agranat |
| Resolution: | Community Answered | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
I have just tried to install MongoDB on a fresh Ubuntu 18 machine. For this I went through the tutorial from the website: https://docs.mongodb.com/manual/tutorial/install-mongodb-on-ubuntu/#install-mongodb-community-edition-using-deb-packages Everything went fine - including starting the server with
and checking that it runs with:
Only I can't seem to start a mongo console. When I type mongo, I get the following error:
I checked for the suggested link but there seems to be no limitation problem as resources are not limited (as per check with ulimit). Machine has 16Gb RAM. Any idea what the problem/solution might be?
|
| Comments |
| Comment by Dmitry Agranat [ 21/Jul/20 ] | |
|
The SERVER project is for bugs and feature suggestions for the MongoDB server. This sounds like a configuration issue related ulimit setting. As this ticket does not appear to be a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Community Forums or on Stack Overflow with the mongodb tag. Regards, | |
| Comment by Vincent Liagre [ 20/Jul/20 ] | |
|
Hi Dmitry, Thank you for getting back to me. I am a bit confused. 1) What do you mean here: "could you please post the requested output together with the executed command of cat /proc/$pid/limits?" ? It's precisely what I did in my previous post, or I am missing something... 2) "would you please archive (tar or zip) the mongod.log files" ; I have no clue where to find those ; could you help me with this? 3) "and the $dbpath/diagnostic.data directory" : same problem here. Thank you for all the help, Best, Vincent | |
| Comment by Dmitry Agranat [ 20/Jul/20 ] | |
|
Hi liagre.vincent@gmail.com, could you please post the requested output together with the executed command of cat /proc/$pid/limits? Also, would you please archive (tar or zip) the 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. Thanks, | |
| Comment by Vincent Liagre [ 20/Jul/20 ] | |
|
Hello Dmitry,
Thank you for getting back to me on this. The limits are: Limit Soft Limit Hard Limit Units | |
| Comment by Dmitry Agranat [ 19/Jul/20 ] | |
|
Could you please provide the output for mongod process limits?
Where pid is the process id of mongod Thanks, |