blocks|key|19865|text|sudo+chmod+777+/data/db/+|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|19866|应该可以在Mac上运行。在运行此cmd之前，权限如下所示|unstyled|19867|drwxr-xr-x++X+User++wheel++Date+/data/db|19868|在运行cmd之后|19869|drwxrwxrwx++X+User++wheel++Date+/data/db|19870|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|P|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|I|3|J|5|F|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$B|C]]|$1|M|3|-4|5|F|7|T|8|@]|9|@]|A|$]]]|N|$]]

<pre><code>sudo chmod 777 /data/db/ 
</code></pre>

Should work on Mac. Before running this cmd, permissions look like

<pre><code>drwxr-xr-x X User wheel Date /data/db
</code></pre>

after running the cmd

<pre><code>drwxrwxrwx X User wheel Date /data/db
</code></pre>

blocks|key|19782|text|这就是对我有效的方法。我用的是Mac，不过如果你用的是windows，你可以试试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|19783|sudo+chmod+777+/data/db|code-block|syntax|javascript|19784|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This is what worked for me. I am using a Mac, although you could try if you're using windows.

<pre><code>sudo chmod 777 /data/db
</code></pre>

blocks|key|19905|text|有三类用户:所有者、组中的用户和其他所有人；chmod+777+/path/to/file允许每个人读/写文件，但chmod+775+/path/to/file只允许所有者/组读/写文件。如果你正在开发一个web服务器，一定要使用chmod+775+/path/to/file。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|19906|一些有用的读物，特别是关于为什么使用777、775等而不是其他数字的推理：https://www.maketecheasier.com/file-permissions-what-does-chmod-777-means/|19907|entityMap|0|LINK|mutability|MUTABLE|url|https://www.maketecheasier.com/file-permissions-what-does-chmod-777-means/^0|M|N|1L|N|37|N|0|11|22|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

There are three categories of users: owners, those in the group, and everyone else; <code>chmod 777 /path/to/file</code> lets everyone read/write the file, but <code>chmod 775 /path/to/file</code> lets only the owner/group read/write the file. Definitely use <code>chmod 775 /path/to/file</code> if you're developing a web server.

Some useful reading, especially for reasoning behind why 777, 775, and so on are used rather than other numbers: <a href="https://www.maketecheasier.com/file-permissions-what-does-chmod-777-means/" rel="nofollow noreferrer">https://www.maketecheasier.com/file-permissions-what-does-chmod-777-means/</a>

blocks|key|19951|text|这些建议都不正确，mongodb-org-3.4.16-1.el7.x86_64还有其他问题。它不能以自定义数据库路径开头。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|19952|[root@localhost+vagrant]#+chmod+777+/data/+/data/mongodb
[root@localhost+vagrant]#+chown+mongod:mongod+/data/+/data/mongodb
[root@localhost+vagrant]#+ls+-lad+/data/mongodb/
drwxrwxrwx.+2+mongod+mongod+6+Jul+11+15:24+/data/mongodb/
[root@localhost+vagrant]#++systemctl+start+mongod
Job+for+mongod.service+failed+because+the+control+process+exited+with+error+code.+See+"systemctl+status+mongod.service"+and+"journalctl+-xe"+for+details.
[root@localhost+vagrant]#+stat+/data/mongodb%5EC
[root@localhost+vagrant]#+!tail
tail+/var/log/mongodb/mongod.log
2018-07-11T15:39:10.786%2B0000+I+STORAGE++[initandlisten]+exception+in+initAndListen:+20+Attempted+to+create+a+lock+file+on+a+read-only+directory:+/data/mongodb,+terminating
2018-07-11T15:39:10.786%2B0000+I+NETWORK++[initandlisten]+shutdown:+going+to+close+listening+sockets...
2018-07-11T15:39:10.786%2B0000+I+NETWORK++[initandlisten]+shutdown:+going+to+flush+diaglog...
2018-07-11T15:39:10.786%2B0000+I+CONTROL++[initandlisten]+now+exiting
2018-07-11T15:39:10.786%2B0000+I+CONTROL++[initandlisten]+shutting+down+with+code:100
[root@localhost+vagrant]#+rpm+-qa+%7C+grep+mongo
mongodb-org-tools-3.4.16-1.el7.x86_64
mongodb-org-shell-3.4.16-1.el7.x86_64
mongodb-org-server-3.4.16-1.el7.x86_64
mongodb-org-mongos-3.4.16-1.el7.x86_64
mongodb-org-3.4.16-1.el7.x86_64|code-block|syntax|javascript|19953|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

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.

<pre><code>[root@localhost vagrant]# chmod 777 /data/ /data/mongodb
[root@localhost vagrant]# chown mongod:mongod /data/ /data/mongodb
[root@localhost vagrant]# ls -lad /data/mongodb/
drwxrwxrwx. 2 mongod mongod 6 Jul 11 15:24 /data/mongodb/
[root@localhost vagrant]# systemctl start mongod
Job for mongod.service failed because the control process exited with error code. See "systemctl status mongod.service" and "journalctl -xe" for details.
[root@localhost vagrant]# stat /data/mongodb^C
[root@localhost vagrant]# !tail
tail /var/log/mongodb/mongod.log
2018-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
2018-07-11T15:39:10.786+0000 I NETWORK [initandlisten] shutdown: going to close listening sockets...
2018-07-11T15:39:10.786+0000 I NETWORK [initandlisten] shutdown: going to flush diaglog...
2018-07-11T15:39:10.786+0000 I CONTROL [initandlisten] now exiting
2018-07-11T15:39:10.786+0000 I CONTROL [initandlisten] shutting down with code:100
[root@localhost vagrant]# rpm -qa | grep mongo
mongodb-org-tools-3.4.16-1.el7.x86_64
mongodb-org-shell-3.4.16-1.el7.x86_64
mongodb-org-server-3.4.16-1.el7.x86_64
mongodb-org-mongos-3.4.16-1.el7.x86_64
mongodb-org-3.4.16-1.el7.x86_64
</code></pre>

blocks|key|4527274|text|快跑吧|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4527275|sudo+chown+group:user+/data/db|code-block|syntax|javascript|4527276|其中group是您的用户组|offset|length|style|CODE|4527277|entityMap^0|0|0|2|5|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Just run

<pre><code>sudo chown group:user /data/db
</code></pre>

where <code>group</code> is a group of your user

blocks|key|4527365|text|给出的答案对我都不起作用。我最终将我的个人操作系统用户配置为root用户，然后手动转到db文件夹-右键单击以查看信息-并为自己添加了读写权限。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4527366|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|19978|text|根据Mongodb大学课程M103的说法，权限级别将为|type|unstyled|depth|inlineStyleRanges|entityRanges|data|19979|sudo+chmod+600+/path/to/db|code-block|syntax|javascript|19980|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

According to Mongodb University course M103 the permission level will be
<pre><code>sudo chmod 600 /path/to/db
</code></pre>

I just finished installing MongoDB on OSX and setup a directory structure with <code>sudo mkdir -p /data/db</code>.

When I attempt to run <code>mongod</code> from my user account it returns an error stating that my user account does not have read/write permission to <code>/data/db</code>.

How can I set the proper read/write permissions on my account for <code>/data/db</code>?

Setting read/write permissions on Mongodb folder

数据库

服务器

MongoDB

我刚刚在OSX上安装了MongoDB，并用sudo mkdir -p /data/db设置了一个目录结构。当我尝试从我的用户帐户运行mongod时，它返回一个错误，指出我的用户帐户没有对/data/db的读/写权限。如何在我的帐户上设置适当的/data/db读/写权限

问设置Mongodb文件夹的读写权限
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问设置Mongodb文件夹的读写权限EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问设置Mongodb文件夹的读写权限
EN