Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
3.0.2
-
None
-
CentOS 7, Azure VM
-
Linux
-
Description
Query provided in "Steps to reproduce" crushes server.
There is output of server log with verbosity at level 5 is attached as file (starting only from a command execution).
Problem occur only if Mongod starts as service (service mongod start), if mongod started in following way:
sudo su -s /bin/bash mongod
mongod -f /etc/mongod.conf
Then query successfully runs; however service mongod status returns "inactive (dead)".
ulimits set according to documentation, mongod is an owner of Data folder, and mongod never runs on same data path as different users.
Another problem with running as service did come up during deployment, and may have something in common with described issue: if run as service, mongod is unable to create lock file and database in any other folder then default /var/lib/ even if mongod is assign owner recursively of new db path .