blocks|key|137360|text|感谢@wdberkeley和@anhlc提出的线索。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|137361|我查看了/var/+log+/mongodb/mongod.log下的日志文件。它显示了问题的失败原因。|137362|2015-03-17T16:08:17.274-0400+I+CONTROL++[initandlisten]+options:+{+config:+"/etc/mongod.conf",+net:+{+bindIp:+"127.0.0.1,+192.168.184.155"+},+storage:+{+dbPath:+"/var/lib/mongodb"+},+systemLog:+{+destination:+"file",+logAppend:+true,+path:+"/var/log/mongodb/mongod.log"+}+}
2015-03-17T16:08:17.332-0400+I+NETWORK++[initandlisten]+getaddrinfo("+192.168.184.155")+failed:+Name+or+service+not+known|code-block|syntax|javascript|137363|所以mongo.conf文件对空格很敏感，这是我碰巧添加的，应该已经注意到了。同样，正如@anhlc指出的那样，96.88.169.145不是VM的有效IP地址。因此，这也会导致错误。|137364|非常感谢你们的帮助！如果有人碰巧遇到了同样的问题，希望这能有所帮助。|137365|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Thanks for @wdberkeley and @anhlc brought up the clue.

I looked at the log file under /var/log/mongodb/mongod.log. It shows the failing reason for the problem.

<pre><code>2015-03-17T16:08:17.274-0400 I CONTROL [initandlisten] options: { config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1, 192.168.184.155" }, storage: { dbPath: "/var/lib/mongodb" }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongod.log" } }
2015-03-17T16:08:17.332-0400 I NETWORK [initandlisten] getaddrinfo(" 192.168.184.155") failed: Name or service not known
</code></pre>

So the mongo.conf file is sensitive to space, which I happened to add and should have noticed. Also just as @anhlc pointed out, 96.88.169.145 is not a valid IP address for VM. So that one also contribute to the error.

Great thanks for both of your help! Hope this may help if someone happened to run into the same problem.

blocks|key|137371|text|如果您只想通过网络连接到这台机器，那么您需要修改bind_ip的值，而不是。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|137372|在您的情况下，您需要遵循以下步骤。|137373|137374|将远程计算机设置为阻止与端口27017的所有连接|ordered-list-item|137375|允许远程计算机仅接受来自本地计算机的连接|137376|设置凭据带有使用credentials.|137377|的客户端的MongoDB|137378|Connect|unordered-list-item|137379|137380|如果您不确定如何执行这些步骤。请查看我写的一篇博客文章，其中详细介绍了如何做到这一点。|137381|Blog+Post|137382|希望这能有所帮助。|137383|entityMap|0|LINK|mutability|MUTABLE|url|http://codewithintent.com/how-to-setup-access-to-mongodb-in-production-with-local-clients-robomongo-humongous-io/^0|O|7|11|1|0|0|H|0|0|0|O|0|0|K|0|0|K|0|0|C|0|0|7|0|0|0|17|0|0|9|0|9|0|0|0|9|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|1F|8|@$9|1G|A|1H|B|D]]|E|@]|F|$]]|$1|I|3|-4|5|6|7|1I|8|@]|E|@]|F|$]]|$1|J|3|K|5|L|7|1J|8|@$9|1K|A|1L|B|D]]|E|@]|F|$]]|$1|M|3|N|5|L|7|1M|8|@$9|1N|A|1O|B|D]]|E|@]|F|$]]|$1|O|3|P|5|L|7|1P|8|@$9|1Q|A|1R|B|D]]|E|@]|F|$]]|$1|Q|3|R|5|6|7|1S|8|@$9|1T|A|1U|B|D]]|E|@]|F|$]]|$1|S|3|T|5|U|7|1V|8|@$9|1W|A|1X|B|D]]|E|@]|F|$]]|$1|V|3|-4|5|6|7|1Y|8|@]|E|@]|F|$]]|$1|W|3|X|5|6|7|1Z|8|@$9|20|A|21|B|D]]|E|@]|F|$]]|$1|Y|3|Z|5|6|7|22|8|@$9|23|A|24|B|D]]|E|@$9|25|A|26|1|27]]|F|$]]|$1|10|3|11|5|6|7|28|8|@$9|29|A|2A|B|D]]|E|@]|F|$]]|$1|12|3|-4|5|6|7|2B|8|@]|E|@]|F|$]]]|13|$14|$5|15|16|17|F|$18|19]]]]

If all you want to do is connect to this machine over the network you do NOT need to modify the <code>bind_ip</code> value.
In your case you need to follow the following steps.
<ol>
<li>Setup the remote machine to block all connections to port 27017</li>
<li>Enable remote machine to only accept connections from your local machine</li>
<li>Setup credentials with MongoDB</li>
<li>Connect with client using credentials.</li>
</ol>
If you are not sure how to do any of this steps. Check out a blog post that I wrote that goes more in details how to do this.
<h1><a href="http://codewithintent.com/how-to-setup-access-to-mongodb-in-production-with-local-clients-robomongo-humongous-io/" rel="nofollow noreferrer">Blog Post</a></h1>
Hope this helps.

blocks|key|2709684|text|您可以通过以下方式完成此操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2709685|bindIp:+[172.31.60.184,127.0.0.1]|code-block|syntax|javascript|2709686|记住不要在逗号后面加空格。|2709687|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You can do that by:

<pre><code>bindIp: [172.31.60.184,127.0.0.1]
</code></pre>

Remember to not put a space after the comma.

blocks|key|2709704|text|用括号包装逗号分隔的-Ips在mongo+3.2.7中对我有效：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2709705|bindIp+=+[127.0.0.1,+192.168.184.155,+96.88.169.145]|code-block|syntax|javascript|2709706|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|$]]

Wrap the comma-separated-Ips with brackets works in mongo 3.2.7 for me:

<pre><code>bindIp = [127.0.0.1, 192.168.184.155, 96.88.169.145]
</code></pre>

blocks|key|138769|text|我使用逗号、无空格和FQDN成功地在我的3.2版服务上添加了第二个ip|type|unstyled|depth|inlineStyleRanges|entityRanges|data|138770|net:
++port:+27017
++bindIp:+localhost,dev-2.office.sampleorg.com|code-block|syntax|javascript|138771|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|$]]

I successfully added a second ip on my version 3.2 service using a comma, no spaces and an FQDN

<pre><code>net:
 port: 27017
 bindIp: localhost,dev-2.office.sampleorg.com
</code></pre>

blocks|key|2709759|text|我在SUSE+12.x上运行3.6，在使用逗号分隔的IP列表时遇到问题。我通过bindIp修复了这个问题:+0.0.0.0|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2709760|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|$]]

I am running 3.6 on SUSE 12.x and had an issues using comma separated IP lists. I fixed the issue by
 bindIp: 0.0.0.0

blocks|key|2922528|text|在Mongo+3.*中，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2922529|使用括号，如|2922530|net:
++++port:+27017
++++bindIp+:+[127.0.0.1,10.0.0.2,10.0.0.3]|code-block|syntax|javascript|2922531|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In Mongo 3.*,

use a bracket such as

<pre><code>net:
 port: 27017
 bindIp : [127.0.0.1,10.0.0.2,10.0.0.3]
</code></pre>

blocks|key|138829|text|在我的Ubuntu16.04LTS上的MongoDB3.6版中的情况是，你不需要把IP地址放在方括号"[]“中。删除逗号日志后的空格，解决mongod日志(/var//mongodb/mongod.log)中连接失败的问题|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|138830|NETWORK++[initandlisten]+getaddrinfo("+xxx.xxx.xxx.xxx")+failed:+Name+or+service+not+known|code-block|syntax|javascript|138831|将bindIp:+127.0.0.1修改为bindIp:+127.0.0.1,xxx.xxx.xxx.xxx+(注意IP之间没有逗号)后，主机IP正在监听，如下所示：|CODE|138832|xxx@xxxx:/var/log/mongodb$+sudo+netstat+-plnt+%7Cegrep+mongod
tcp++++++++0++++++0+xxx.xxx.xxx.xxx:27017+++0.0.0.0:*+++++++++++++++LISTEN++++++30747/mongod++++
tcp++++++++0++++++0+127.0.0.1:27017+++++++++0.0.0.0:*+++++++++++++++LISTEN++++++30747/mongod+|138833|entityMap^0|J|B|1K|R|0|0|1|H|L|X|1J|C|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|W|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|X|8|@$9|Y|A|Z|B|M]|$9|10|A|11|B|M]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|N|3|O|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|P|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|Q|$]]

The case in mongodb version 3.6 on my Ubuntu16.04 LTS is that you do not need to put the IP addresses in the square brackets "[]". Delete the space after the comma solve the failed connection problem in the mongod log (/var/log/mongodb/mongod.log)

<pre><code>NETWORK [initandlisten] getaddrinfo(" xxx.xxx.xxx.xxx") failed: Name or service not known
</code></pre>

After modify the <code>bindIp: 127.0.0.1</code> to <code>bindIp: 127.0.0.1,xxx.xxx.xxx.xxx</code> (notice no comma between IPs), the host IP is listening as below:

<pre><code>xxx@xxxx:/var/log/mongodb$ sudo netstat -plnt |egrep mongod
tcp 0 0 xxx.xxx.xxx.xxx:27017 0.0.0.0:* LISTEN 30747/mongod 
tcp 0 0 127.0.0.1:27017 0.0.0.0:* LISTEN 30747/mongod 
</code></pre>

blocks|key|138848|text|在我的例子中，解决方案是将逗号分隔的IP放在一起，并且不带任何空格。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|138849|bind_ip=192.168.2.29,127.0.0.1
#port+=+27017|code-block|syntax|javascript|138850|这种方式起作用了：|138851|2018-10-02T07:49:27.952%2B0000+I+CONTROL++[initandlisten]+options:+{+config:+"/etc/mongodb.conf",+net:+{+bindIp:+"192.168.2.29,127.0.0.1",+unixDomainSocket:+{+pathPrefix:+"/run/mongodb"+}+},+storage:+{+dbPath:+"/var/lib/mongodb",+journal:+{+enabled:+true+}+},+systemLog:+{+destination:+"file",+logAppend:+true,+path:+"/var/log/mongodb/mongodb.log"+}+}+2018-10-02T07:49:27.954%2B0000+I+-++++[initandlisten]+Detected+data+files+in+/var/lib/mongodb+created+by+the+'wiredTiger'+storage+engine,+so+setting+the+active+storage+engine+to+'wiredTiger'.|138852|这里是Mongo+3.6.3。|138853|OpenSSL+--版本数据库版本v3.6.3+git版本:+9586e557d54ef70f9ca4b43c26892cd55257e1a5分配器版本:+OpenSSL+1.1.0g+2+Nov+2017分配器:+tcmalloc模块:无构建环境:+distarch:+x86_64+target_arch:+x86_64|138854|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

In my case the solution was to put the comma separated IP and without any spaces. 

<pre><code>bind_ip=192.168.2.29,127.0.0.1
#port = 27017
</code></pre>

That way worked:

<pre><code>2018-10-02T07:49:27.952+0000 I CONTROL [initandlisten] options: { config: "/etc/mongodb.conf", net: { bindIp: "192.168.2.29,127.0.0.1", unixDomainSocket: { pathPrefix: "/run/mongodb" } }, storage: { dbPath: "/var/lib/mongodb", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongodb.log" } } 2018-10-02T07:49:27.954+0000 I - [initandlisten] Detected data files in /var/lib/mongodb created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
</code></pre>

Mongo 3.6.3 here. 

mongod --version
db version v3.6.3
git version: 9586e557d54ef70f9ca4b43c26892cd55257e1a5
OpenSSL version: OpenSSL 1.1.0g 2 Nov 2017
allocator: tcmalloc
modules: none
build environment:
 distarch: x86_64
 target_arch: x86_64

blocks|key|137553|text|Ubuntu+16.04+->+MongoDB外壳版本:+2.6.10|type|unstyled|depth|inlineStyleRanges|entityRanges|data|137554|对我来说，以下是工作：|137555|bind_ip+=127.0.0.1；X.X|137556|注意，我有一个;，而不是,|offset|length|style|CODE|137557|entityMap^0|0|0|0|7|1|C|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@$H|R|I|S|J|K]|$H|T|I|U|J|K]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|M|$]]

Ubuntu 16.04 -> MongoDB shell version: 2.6.10

For me the following works:

<h3>bind_ip = [127.0.0.1;X.X.X.X]</h3>

Notice I have a <code>;</code> not <code>,</code>

blocks|key|2922717|text|使用以下版本的MongoDB:+MongoDB+shell版本v3.6.10|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2922718|再现问题：当使用127.0.0.1，xxx.xxx时，我们得到以下错误。标量选项“net.bindIp”必须是单个值。有关详细信息，请尝试“mongod-help”|offset|length|style|BOLD|2922719|分析这是因为，根据MongoDB文档：https://docs.mongodb.com/manual/reference/configuration-options/#net.bindIP|CODE|2922720|net.bindIP类型为"string“。|2922721|绑定多个IP地址的解决方案|2922722|bindIp:+"127.0.0.1,xxx.xxx.xxx.xxx"|code-block|syntax|javascript|2922723|注意:逗号后没有空格|2922724|entityMap^0|0|0|5|0|0|2|J|23|0|E|6|0|9|4|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@$D|12|E|13|F|G]|$D|14|E|15|F|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1C|8|@]|9|@]|A|$R|S]]|$1|T|3|U|5|6|7|1D|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|W|$]]

With the following version of MongoDB:
MongoDB shell version v3.6.10

Reproducing Problem:
When [127.0.0.1,xxx.xxx.xxx.xxx] is used we get the following error.
 Scalar option 'net.bindIp' must be a single value
 try 'mongod --help' for more information

Analysis
This is because, according to MongoDB Documentation: <code>https://docs.mongodb.com/manual/reference/configuration-options/#net.bindIP</code>

net.bindIP is of type "string".

Solution for binding multiple IP Addresses

<pre><code>bindIp: "127.0.0.1,xxx.xxx.xxx.xxx"
</code></pre>

Note: No spaces after commas

blocks|key|2710043|text|使用逗号分隔IP地址的bindIp规则仅适用于已知以太网接口，或者适用于0.0.0.0和127.0.0.1规则。您只能使用系统网卡的ip地址。如果此列表包含未知的IP地址，即另一个系统的IP，则您的MongoDb实例将不会重启，因此您无法连接。要检查您的MongoDb实例是否正在运行，请运行以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2710044|$+sudo+systemctl+status+mongod|code-block|syntax|javascript|2710045|如果您希望您的MongoDb实例可供网络上的其他系统使用，则需要绑定与内网关联的本地IP。要轻松确定网络接口配置，只需从命令行运行ifconfig：|2710046|$+ifconfig|2710047|这将列出您可以在bindIp规则中使用的所有可用IP地址。可以肯定的是，您使用的IP地址96.88.169.145不是有效的IP地址或系统未知。|2710048|entityMap^0|0|0|0|0|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|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The bindIp rule with comma separated IP addresses is only meant for known ethernet interfaces, or for the 0.0.0.0 and 127.0.0.1 rules. You can only use the ip addresses of your system's Network Interface Cards. If this list contains an unknown IP address, i.e. an IP of another system, your MongoDb instance will not restart and hence you're not able to connect. To check if your MongoDb instance is running, run the following:

<pre><code>$ sudo systemctl status mongod
</code></pre>

If you would like to make your MongoDb instance available to other systems on your network, you'll want to bind the local IP associated with the private network. To determine network interface configuration easily, just run an ifconfig from the command line:

<pre><code>$ ifconfig
</code></pre>

This will list all available IP addresses that you can use in the bindIp rule. Most certainly, the IP address 96.88.169.145 that you use is not a valid IP address or unknown by your system.

blocks|key|138958|text|对于那些仍然想知道的人来说-的问题不是在语法上，而是你输入的地址。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|138959|阅读this+answer|138960|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/58733377/2520497^0|E|I|0|2|B|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@$9|T|A|U|1|V]]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

For those who still wondering - problem is not in the syntax, but the addresses you put in.

Read <a href="https://stackoverflow.com/a/58733377/2520497">this answer</a>

blocks|key|140008|text|Amazon-linux2+%7C+Cent+OS+%7C+MongoDB外壳版本:+3.0.15|type|unstyled|depth|inlineStyleRanges|entityRanges|data|140009|这就是在最新的配置中需要做的|140010|#network+interfaces
net:
++port:+27017
++bindIp:+[xxx.xxx.xxx.xxx,127.0.0.1]++#+Listen+to+local+interface+only,+comment+to+listen+on+all+interfaces.|code-block|syntax|javascript|140011|干杯！！|140012|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Amazon-linux2 | Cent OS | MongoDB shell version: 3.0.15
This is how it needs to be done in the latest config
<pre><code>#network interfaces
net:
 port: 27017
 bindIp: [xxx.xxx.xxx.xxx,127.0.0.1] # Listen to local interface only, comment to listen on all interfaces.
</code></pre>
Cheers!!

blocks|key|2922810|text|默认的/etc/mongod.conf文件包含以下网络接口条目：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2922811|#+network+interfaces
net:
++port:+27017
++bindIp:+127.0.0.1|code-block|syntax|javascript|2922812|这与命令行上的--bind-ip+arg参数相对应。请注意，破折号符号转换为驼峰式大小写。要向主机公开在VM中运行的数据库，最简单的方法是将数据库绑定到所有接口以进行测试。这将涵盖VM使用NAT接口或桥接接口的情况。命令行参数是没有参数的--bind_ip_all，它的存在对应于配置文件中的bindIPAll:+true参数。因此，配置文件应更改为：|offset|length|style|CODE|2922813|#+network+interfaces
net:
++port:+27017
++bindIpAll:+true|2922814|请注意，bindIp参数已删除。|2922815|还应注意，可以将参数添加到命令行以覆盖配置文件中的参数。通常情况下，mongod是使用--config+/etc/mongod.conf参数运行的。更改配置文件比寻找将其作为守护进程运行的脚本并让systemd重新加载和使用它要容易得多。|2922816|有关配置文件的YAML-ness与命令行参数的详细信息，请参阅当前位于https://docs.mongodb.com/manual/reference/configuration-options/的文档|2922817|如果您在使用NAT的VM上运行mongod，则默认端口27017将不会暴露给主机。需要将主机上的端口映射到来宾虚拟机中的此端口。这超出了本答案的范围，但稍微研究一下就会提供一种用于您正在使用的VM软件(VirtualBox、VMware等)的方法。|2922818|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.mongodb.com/manual/reference/configuration-options/^0|0|0|7|D|3B|D|42|F|0|0|4|6|0|17|P|2Q|7|0|Z|1S|0|0|R|5|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@$I|17|J|18|K|L]|$I|19|J|1A|K|L]|$I|1B|J|1C|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1E|8|@$I|1F|J|1G|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1H|8|@$I|1I|J|1J|K|L]|$I|1K|J|1L|K|L]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1M|8|@]|9|@$I|1N|J|1O|1|1P]]|A|$]]|$1|U|3|V|5|6|7|1Q|8|@$I|1R|J|1S|K|L]]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

The default /etc/mongod.conf file has this entry for network interfaces:
<pre><code># network interfaces
net:
 port: 27017
 bindIp: 127.0.0.1
</code></pre>
This corresponds to the <code>--bind-ip arg</code> parameter on the command line. Notice the dash notation converted to camel case. To expose the database running in a VM to the host, it's simplest to bind the database to all interfaces for testing purposes. This will cover situations where the VM is using a NAT interface or bridged interface. The command line parameter is <code>--bind_ip_all</code> which does not have a parameter, it's existence corresponds to the <code>bindIPAll: true</code> parameter in the configuration file. Therefore, the configuration file should be changed to:
<pre><code># network interfaces
net:
 port: 27017
 bindIpAll: true
</code></pre>
Notice the <code>bindIp</code> parameter is removed.
It should also be noted that it is possible to add parameters to the command line that override parameters in the config file. Normally, mongod is run with the <code>--config /etc/mongod.conf</code> parameter. It's easier to change the config file instead of hunting down the script what runs it as a daemon and getting <code>systemd</code> to reload and use it.
For details on the YAML-ness of the config file vs. parameters on the command line, see the documentation currently at <a href="https://docs.mongodb.com/manual/reference/configuration-options/" rel="nofollow noreferrer">https://docs.mongodb.com/manual/reference/configuration-options/</a>
If you are running mongod on a VM using NAT, the default port <code>27017</code> will not be exposed to the host. It will be necessary to map a port on the host to this port in the guest VM. That's beyond the scope of this answer, but a little research will provide a method used for the VM software you are using (VirtualBox, VMware, etc.)

blocks|key|137633|text|对于MongoDB服务器版本:+3.6.8简单的逗号分隔列表适用于我。逗号后有或没有空格。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|137634|bind_ip+=+127.0.0.1,+192.168.0.104
bind_ip+=+127.0.0.1,192.168.0.104|code-block|syntax|javascript|137635|但是，在[]中添加封闭失败，并在MongoDB日志中显示以下错误|offset|length|style|CODE|137636|bind_ip+=+[127.0.0.1,192.168.0.104]
getaddrinfo("[127.0.0.1")+failed:+Name+or+service+not+known

bind_ip+=+[127.0.0.1,+192.168.0.104]
getaddrinfo("[127.0.0.1")+failed:+Name+or+service+not+known|137637|entityMap^0|0|0|4|2|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

With MongoDB server version: 3.6.8 plain comma separated list worked for me. With or without spaces after comma.
<pre><code>bind_ip = 127.0.0.1, 192.168.0.104
bind_ip = 127.0.0.1,192.168.0.104
</code></pre>
However, adding enclosing in <code>[]</code> fails with following error in MongoDB log
<pre><code>bind_ip = [127.0.0.1,192.168.0.104]
getaddrinfo(&quot;[127.0.0.1&quot;) failed: Name or service not known

bind_ip = [127.0.0.1, 192.168.0.104]
getaddrinfo(&quot;[127.0.0.1&quot;) failed: Name or service not known
</code></pre>

blocks|key|140061|text|对于4.4.6，让我们假设是4.x系列(可能是3.x系列的一些)|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|140062|正确的语法是：|140063|140064|bindIp:+127.0.0.1,<private_host_ip>,<public_host_ip>|unordered-list-item|140065|140066|对于每个新IP，只需使用,，不带任何空格|140067|对于局域网访问必须使用private_host_ip，可以分别使用ipconfig或ip+a来了解IP值。当然对于公用的广域网接入一定要用<public_host_ip>，这是关于你的运营商的|140068|Warning+ips+-+private_host_ip和<public_host_ip>+-是运行MongoDB服务器的位置，而不是远程客户端。因此，存在添加每个新ip的错误假设，其中每个IP代表远程客户端+IP地址(不同于服务器IP地址-局域网和/或广域网)，这是不正确的。|BOLD|140069|注意避免的问题，最好既使用静态ips，将私有ips通过您的路由器，第二次通过您的互联网服务提供商。|140070|entityMap^0|2|5|0|0|0|0|1G|0|0|C|1|0|B|F|X|8|16|4|1X|G|0|0|7|1F|7|2U|3|36|3|3V|1|E|F|U|G|0|0|1D|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|12|8|@$9|13|A|14|B|C]]|D|@]|E|$]]|$1|L|3|-4|5|6|7|15|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1I|8|@$9|1J|A|1K|B|S]|$9|1L|A|1M|B|S]|$9|1N|A|1O|B|S]|$9|1P|A|1Q|B|S]|$9|1R|A|1S|B|S]|$9|1T|A|1U|B|C]|$9|1V|A|1W|B|C]]|D|@]|E|$]]|$1|T|3|U|5|6|7|1X|8|@$9|1Y|A|1Z|B|S]]|D|@]|E|$]]|$1|V|3|-4|5|6|7|20|8|@]|D|@]|E|$]]]|W|$]]

For <code>4.4.6</code>, so - lets assume for series 4.x (perhaps for some of series 3.x)
The correct syntax is:
<ul>
<li><code>bindIp: 127.0.0.1,&lt;private_host_ip&gt;,&lt;public_host_ip&gt;</code></li>
</ul>
For each new IP just use <code>,</code> and without any spaces
For LAN access must be used the <code>private_host_ip</code>, you can use <code>ipconfig</code> or <code>ip a</code> for Windows and Linux respectively to know the ip value.
Of course for public WAN access must be used <code>&lt;public_host_ip&gt;</code>, it about your ISP
Warning both ips - <code>private_host_ip</code> and <code>&lt;public_host_ip&gt;</code> - are the locations where your MongoDB server is running, not the remote clients. Therefore exists the wrong assumption to add each new ip where each one represents the remote client IP address (other different than the server IP address - LAN and/or WAN), it is not correct.
Note To avoid problems is better for both use static ips, the private through your router and the second through your ISP.

blocks|key|2710193|text|在我的例子中，使用mongoDB+4.4.6下面的解决方案-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2710194|net:
++port:+27017
++bindIp:+127.0.0.1;<private_host_ip>|code-block|syntax|javascript|2710195|进行更改后，使用以下命令重新启动mongoDB+-|2710196|sudo+systemctl+restart+mongod|2710197|要检查mongoDB状态，请运行-|2710198|sudo+systemctl+status+mongod|2710199|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

In my case, with mongoDB 4.4.6 following solution worked -
<pre><code>net:
 port: 27017
 bindIp: 127.0.0.1;&lt;private_host_ip&gt;
</code></pre>
After making changes, restart mongoDB with following command -
<pre><code>sudo systemctl restart mongod
</code></pre>
To Check mongoDB status, run -
<pre><code>sudo systemctl status mongod
</code></pre>

I am a newbie for setting up the server environment and mongoDB. This may sounds something really simple, however, I really need your help on it.

I am trying to connect to my virtual machine which runs the mongodb instance from the local machine, which I believe should be similar to the production environment when I run it on a separate remote server.

The environment is as following:

<ul>
<li>Private IP for virtual machine: 192.168.184.155</li>
<li>Public IP for both local machine and virtual machine: 96.88.169.145</li>
</ul>

 

I changed the bind_ip in /etc/mongod.conf file from

<pre><code>bind_ip = 127.0.0.1
</code></pre>

to

<pre><code>bind_ip = 127.0.0.1,192.168.184.155,96.88.169.145
</code></pre>

After I restarted the mongod service, neither the virtual machine nor the local machine can access mongodb through mongodb command and giving me the following error.

<pre><code>MongoDB shell version: 3.0.1
connecting to: test
2015-03-17T16:02:22.705-0400 W NETWORK Failed to connect to 127.0.0.1:27017, reason: errno:111 Connection refused
2015-03-17T16:02:22.707-0400 E QUERY Error: couldn't connect to server 127.0.0.1:27017 (127.0.0.1), connection attempt failed
 at connect (src/mongo/shell/mongo.js:179:14)
 at (connect):1:6 at src/mongo/shell/mongo.js:179
exception: connect failed
</code></pre>

However, if I change the 

<pre><code>bind_ip = 192.168.184.155
</code></pre>

and restart the service, it works and I can access using mongo from my local machine. It seems just not work with multiple ip addresses. I tried to do look up in the mongodb document, however, they does mention that bind_ip takes a comma separated list, which really confused me.

Thanks for your help in advance.

How to set mongod.conf bind_ip with multiple ip address

我是设置服务器环境和mongoDB的新手。这可能听起来很简单，但是，我真的需要你的帮助。我正在尝试连接到我的虚拟机，它从本地机器运行mongodb实例，我相信当我在单独的远程服务器上运行它时，它应该类似于生产环境。环境如下：虚拟机的专用IP :本地和虚拟机的192.168.184.155Public IP : 96.8...

问如何设置具有多个ip地址的mongod.conf bind_ip
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何设置具有多个ip地址的mongod.conf bind_ipEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何设置具有多个ip地址的mongod.conf bind_ip
EN