I just finished installing MongoDB on OSX and setup a directory structure with sudo mkdir -p /data/db.
When I attempt to run mongod from my user account it returns an error stating that my user account does not have read/write permission to /data/db.
How can I set the proper read/write permissions on my account for /data/db?
Artem :
Just run\n\nsudo chown group:user /data/db\n\n\nwhere group is a group of your user",
2015-03-11T14:05:13
suzmas :
None of the given answers were working for me. I ended up configuring my personal OS user to be the root user, then manually went to the db folder - right clicked to view info - and added myself with read and write permissions.",
2017-01-13T06:40:32
davidcondrey :
Ensure that user account running mongod has the proper directory permissions. You can check which permissions are set like so:\n\nls -ld /data/db/\n\n\nIf they are set properly they should look something like this..\n\n\n drwxr-xr-x X user wheel XXX Date Time /data/db/\n\n\nIf the permissions are set incorrectly you will likely see an error similar to this when attempting to run mongod\n\n\n exception in initAndListen: XXXXX Unable to create/open lock file: /data/db/mongod.lock errno:13 Permission denied Is a mongod instance already running?, terminating\n\n\nTo get the permissions set as they should be you can run the following command\n\nsudo chmod 0755 /data/db && sudo chown $USER /data/db\n",
2015-03-12T06:52:05
getSantsoh :
sudo chmod 777 /data/db/ \n\n\nShould work on Mac. Before running this cmd, permissions look like\n\ndrwxr-xr-x X User wheel Date /data/db\n\n\nafter running the cmd\n\ndrwxrwxrwx X User wheel Date /data/db\n",
2017-01-28T23:57:36
Tim Anishere :
This is what worked for me. I am using a Mac, although you could try if you're using windows.\n\nsudo chmod 777 /data/db\n",
2016-06-21T05:07:23
aaron :
There are three categories of users: owners, those in the group, and everyone else; chmod 777 /path/to/file lets everyone read/write the file, but chmod 775 /path/to/file lets only the owner/group read/write the file. Definitely use chmod 775 /path/to/file if you're developing a web server.\n\nSome useful reading, especially for reasoning behind why 777, 775, and so on are used rather than other numbers: https://www.maketecheasier.com/file-permissions-what-does-chmod-777-means/",
2017-08-16T17:16:03
b__ :
None of these suggestions are correct, there's something else wrong with mongodb-org-3.4.16-1.el7.x86_64. It cannot start with a custom db path.\n\n[root@localhost vagrant]# chmod 777 /data/ /data/mongodb\n[root@localhost vagrant]# chown mongod:mongod /data/ /data/mongodb\n[root@localhost vagrant]# ls -lad /data/mongodb/\ndrwxrwxrwx. 2 mongod mongod 6 Jul 11 15:24 /data/mongodb/\n[root@localhost vagrant]# systemctl start mongod\nJob for mongod.service failed because the control process exited with error code. See \"systemctl status mongod.service\" and \"journalctl -xe\" for details.\n[root@localhost vagrant]# stat /data/mongodb^C\n[root@localhost vagrant]# !tail\ntail /var/log/mongodb/mongod.log\n2018-07-11T15:39:10.786+0000 I STORAGE [initandlisten] exception in initAndListen: 20 Attempted to create a lock file on a read-only directory: /data/mongodb, terminating\n2018-07-11T15:39:10.786+0000 I NETWORK [initandlisten] shutdown: going to close listening sockets...\n2018-07-11T15:39:10.786+0000 I NETWORK [initandlisten] shutdown: going to flush diaglog...\n2018-07-11T15:39:10.786+0000 I CONTROL [initandlisten] now exiting\n2018-07-11T15:39:10.786+0000 I CONTROL [initandlisten] shutting down with code:100\n[root@localhost vagrant]# rpm -qa | grep mongo\nmongodb-org-tools-3.4.16-1.el7.x86_64\nmongodb-org-shell-3.4.16-1.el7.x86_64\nmongodb-org-server-3.4.16-1.el7.x86_64\nmongodb-org-mongos-3.4.16-1.el7.x86_64\nmongodb-org-3.4.16-1.el7.x86_64\n",
2018-07-11T15:46:26