You can bring up your server members with authentication options then It is a problem from MongoDB University course “M310: MongoDB Security”. These settings will expire the ulimit settings upon relaunch of the terminal and the launchctl settings upon restart of the computer.I have to start my own replica set with internal authentication enabled using X.509 certificates, but I failed. However, if you wish to change the limit only for the current session, you may skip modifications to files and simply enter the following into the terminal: sudo launchctl limit maxfiles 65536 65536 The above method is suitable for computers that are happy to keep a high open files limit in the long run. You will no longer see soft rlimits warnings when you login into mongo shell with mongo from the command line! You should see confirmed that the maxfiles is 65536.

You need to add the following lines to the end of the file: ulimit -n 65536Īs with the other files above, make sure the bashrc file has -rw-r-r- permissions.Īfter all this is done, restart the computer and type ulimit -n into a terminal. Once system limits are properly set, it remains necessary to set session limits. This can be confirmed by typing launchctl limit into a terminal. ĭoing the above will cause system limits to set themselves correctly upon restart. The chmod command to do that is sudo chmod 644. This should be the default but it's wise to check. Please confirm that both these files are owned by root:wheel and have permissions -rw-r-r. (Source of this how to found at basho/basho_docs#1402) follow this how-to exactly and it will resolve the issue for you. Number of files is 256, should be at least 1000 when you login to mongo shell via mongo from the commandline, or any mysterious/unexplained mongo connection errors. If you are seeing Mongo soft rlimits warnings in your logs, or a WARNING: soft rlimits too low.

Mongodb mac os x soft rlimits too low