mongodb - 无法连接到配置的 mongo 实例(连接被拒绝)

标签 mongodb docker

基于本指南:

https://docs.opsmanager.mongodb.com/current/tutorial/install-simple-test-deployment/

我正在安装 MongoDB 和 MongoDB Manager。我为每个应用程序创建了一个 docker 镜像,并在同一虚拟网络上启动它们:

docker network create --driver bridge mongo-network

与:

MongoDB:

 docker run -ti -d --network mongo-network -p 27017:27017 --name mongodb-container mongodb-image
 docker exec -ti -u mongod mongodb-container "mongod --port 27017 --dbpath /data/appdb --logpath /data/appdb/mongodb.log --wiredTigerCacheSizeGB 1 --fork"

并验证其已启动并运行:

$  docker exec -ti -u mongod mongodb-container tail -f /data/appdb/mongodb.log

2019-04-21T15:26:05.208+0000 I CONTROL  [initandlisten] ** WARNING: This server is bound to localhost.
2019-04-21T15:26:05.208+0000 I CONTROL  [initandlisten] **          Remote systems will be unable to connect to this server. 
2019-04-21T15:26:05.208+0000 I CONTROL  [initandlisten] **          Start the server with --bind_ip <address> to specify which IP 
2019-04-21T15:26:05.208+0000 I CONTROL  [initandlisten] **          addresses it should serve responses from, or with --bind_ip_all to
2019-04-21T15:26:05.208+0000 I CONTROL  [initandlisten] **          bind to all interfaces. If this behavior is desired, start the
2019-04-21T15:26:05.208+0000 I CONTROL  [initandlisten] **          server with --bind_ip 127.0.0.1 to disable this warning.
2019-04-18T06:23:35.268+0000 I CONTROL  [initandlisten] 
2019-04-18T06:23:35.269+0000 I STORAGE  [initandlisten] createCollection: admin.system.version with provided UUID: c0736278-72ec-4dfc-893c-8105eefa0ba8
2019-04-18T06:23:35.320+0000 I COMMAND  [initandlisten] setting featureCompatibilityVersion to 4.0
2019-04-18T06:23:35.341+0000 I STORAGE  [initandlisten] createCollection: local.startup_log with generated UUID: 397c17a3-3c5e-4605-b4dc-8a936dd9e40e
2019-04-18T06:23:35.394+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/appdb/diagnostic.data'
2019-04-18T06:23:35.396+0000 I NETWORK  [initandlisten] waiting for connections on port 27017
2019-04-18T06:23:35.397+0000 I STORAGE  [LogicalSessionCacheRefresh] createCollection: config.system.sessions with generated UUID: ac7bdb6e-4a60-430f-b1a4-34b09012e6da
2019-04-18T06:23:35.475+0000 I INDEX    [LogicalSessionCacheRefresh] build index on: config.system.sessions properties: { v: 2, key: { lastUse: 1 }, name: "lsidTTLIndex", ns: "config.system.sessions", expireAfterSeconds: 1800 }
2019-04-18T06:23:35.475+0000 I INDEX    [LogicalSessionCacheRefresh]     building index using bulk method; build may temporarily use up to 500 megabytes of RAM
2019-04-18T06:23:35.477+0000 I INDEX    [LogicalSessionCacheRefresh] build index done.  scanned 0 total records. 0 secs

MongoDB 管理器:

  docker run -ti -d --network mongo-network -p 8080:8080 --name mongodb-manager-container mongodb-manager-image  
  docker exec -ti -u root mongodb-manager-container "/opt/mongodb/mms/bin/mongodb-mms start"

以下错误消息:

Generating new Ops Manager private key...
Starting pre-flight checks
    Failure to connect to configured mongo instance:Config{
       loadBalance=false,
       encryptedCredentials=false,
       ssl='false',
       dbNames='   [
          mmsdb,
          mmsdbprovisionlog,
          mmsdbautomation,
          mmsdbserverlog,
          mmsdbpings,
          mmsdbprofile,
          mmsdbrrd,
          mmsdbconfig,
          mmsdblogcollection,
          mmsdbjobs,
          mmsdbagentlog,
          mmsdbbilling,
          backuplogs,
          automationcore,
          monitoringstatus,
          mmsdbautomationlog,
          automationstatus,
          ndsstatus,
          cloudconf,
          backupdb,
          mmsdbprovisioning,
          mmsdbqueues
       ]   ',
       uri=mongodb://mongodb-container:27017/?maxPoolSize=150
    }Error:Timed out after 30000 ms while waiting to connect. Client view of cluster state is{
       type=UNKNOWN,
       servers=   [
          {
             address=mongodb-container:27017,
             type=UNKNOWN,
             state=CONNECTING,
             exception=         {
                com.mongodb.MongoSocketOpenException:Exception opening socket
             },
             caused by         {
                java.net.ConnectException:Connection refused (Connection refused)
             }
          }
       ]

对于 mongodb - 基于下面的建议 - 我现在正在使用:

/etc/mongod.conf:

# network interfaces
net:
  port: 27017
  #bindIp: 127.0.0.1  # Enter 0.0.0.0,:: to bind to all IPv4 and IPv6 addresses or, alternatively, use the net.bindIpAll setting.
  bindIp: 0.0.0.0,::

对于 MongoDB 管理器,我在以下位置指定 mongodb 容器的名称:

/opt/mongodb/mms/conf/conf-mms.properties

#mongo.mongoUri=mongodb://127.0.0.1:27017/?maxPoolSize=150
#mongo.mongoUri=mongodb://0.0.0.0:27017/?maxPoolSize=150
mongo.mongoUri=mongodb://mongodb-container:27017/?maxPoolSize=150

我已经验证我可以通过以下方式从 mongodb-manager-container ping mongodb-container:

docker exec -it -u root mongodb-manager-container bash
[root@e23a34bf2161 /]# ping mongodb-container
PING mongodb-container (172.18.0.2) 56(84) bytes of data.
64 bytes from mongodb-container.mongo-network (172.18.0.2): icmp_seq=1 ttl=64 time=0.077 ms
64 bytes from mongodb-container.mongo-network (172.18.0.2): icmp_seq=2 ttl=64 time=0.059 ms
64 bytes from mongodb-container.mongo-network (172.18.0.2): icmp_seq=3 ttl=64 time=0.052 ms
^C
--- mongodb-container ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2042ms
rtt min/avg/max/mdev = 0.052/0.062/0.077/0.013 ms
[root@e23a34bf2161 /]# 

我错过了什么?

编辑:

基于我现在尝试过的以下建议:

docker network create --driver bridge mongo-network
docker run -ti -d --network mongo-network -p 27017:27017 --name mongodb-container mongodb-image
# Copy modified version of mongod.conf file to container before starting mongodb    
docker cp mongod.conf mongodb-container:/etc/mongod.conf

docker exec -ti -u mongod mongodb-container "mongod --port 27017 --dbpath /data/appdb --logpath /data/appdb/mongodb.log --wiredTigerCacheSizeGB 1 --fork"
docker run -it --rm --net container:mongodb-container nicolaka/netshoot ss -lnt

这给出:

State    Recv-Q    Send-Q        Local Address:Port        Peer Address:Port    
LISTEN   0         128              127.0.0.11:36001            0.0.0.0:*       
LISTEN   0         128               127.0.0.1:27017            0.0.0.0:*   

不确定这是否是预期的/良好的输出以及为什么我需要从 nicolaka/netshoot 图像启动容器...

编辑2:

如下所示,如果我在命令行上传递:--bind_ip_all来启动mongod,它就可以工作:

docker exec -ti -u mongod mongodb-container "mongod --bind_ip_all --port 27017 --dbpath /data/appdb --logpath /data/appdb/mongodb.log --wiredTigerCacheSizeGB 1 --fork"

因此,当作为 docker 容器运行时,它似乎完全忽略 /etc/mongod.conf 文件,您需要在 docker exec 命令中指定所有选项:-(

最佳答案

容器名称上的 DNS 将解析为容器 IP。要使用该名称连接到 mongo,即使是从容器内部,您也需要让 mongo 监听所有接口(interface):

# network interfaces
net:
  port: 27017
  bindIp: 0.0.0.0,::

关于mongodb - 无法连接到配置的 mongo 实例(连接被拒绝),我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/55739457/

相关文章:

javascript - sinon 模拟 withArgs 中具有未知值的对象 - sinon.match

mysql - 无法从本地主机连接到 mysql 容器

postgresql - 将 hasura 连接到现有的 postgresql

javascript - MongoDB:具有动态字段名称的 addToSet

mongodb - Mongorestore 在没有 --drop 的情况下更新记录(如果已经存在)

java - ArrayList<Filters> 类型中的方法 add(Filters) 不适用于使用 java 的 mongodb 中的参数 (Bson)?

docker - Traefik v2 反向代理到 Docker 外部的本地服务器

mongodb - 为什么我无法访问在Azure Web应用程序的Docker容器中运行的mongodb?

docker - 带有URL路径的Docker满

docker - 将文件从基础图像复制到当前建筑物图像