[DOCS-9759] Comment on: "manual/reference/configuration-options.txt" Created: 11/Jan/17  Updated: 03/Nov/17  Resolved: 03/Oct/17

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mac OS X 10.10

Location: https://docs.mongodb.com/v3.2/reference/configuration-options/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.95 Safari/537.36
Referrer: https://www.google.com/
Screen Resolution: 2560 x 1440


Issue Links:
Related
related to DOCS-8722 net.ipv6 is used in MongoDB configura... Closed
is related to DOCS-7067 Remove '--ipv6' documentation from al... Closed
Participants:
Days since reply: 6 years, 19 weeks, 2 days ago

 Description   

This page claims IPv6 is enabled by default since 3.0, but I have just tested 3.4.0 on Mac and IPv6 is off. On the command line it requires "--ipv6". I haven't tested how the config file actually works. "mongod --help" says:

  --ipv6                                enable IPv6 support (disabled by
                                        default)



 Comments   
Comment by Githook User [ 03/Oct/17 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}

Message: DOCS-9759, DOCS-8722: fix ipv6 for mongod/mongos erroneously applied via DOCS-7067
Branch: v3.4
https://github.com/mongodb/docs/commit/5eb00761e67ce67a1a40977bffd8bbee43d0d72e

Comment by Githook User [ 03/Oct/17 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}

Message: DOCS-9759, DOCS-8722: fix ipv6 for mongod/mongos erroneously applied via DOCS-7067
Branch: v3.0
https://github.com/mongodb/docs/commit/54f9a4edd0a69259ffbb2c7b973b0ef76cc8d484

Comment by Githook User [ 03/Oct/17 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}

Message: DOCS-9759, DOCS-8722: fix ipv6 for mongod/mongos erroneously applied via DOCS-7067
Branch: v3.2
https://github.com/mongodb/docs/commit/9a55764eb853cd86e2135791fef42cfc38137001

Comment by Githook User [ 03/Oct/17 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'kay', 'username': 'kay-kim'}

Message: DOCS-9759, DOCS-8722: fix ipv6 for mongod/mongos erroneously applied via DOCS-7067
Branch: master
https://github.com/mongodb/docs/commit/f5d8f57ea7cc1b9c54a268693cda826f5bdbec3e

Comment by Kay Kim (Inactive) [ 03/Oct/17 ]

DOCS-7067 accidentally applied tools related change to mongod/mongos.

Comment by Joshua Maag [ 09/Feb/17 ]

I have reproduced this issue with 3.2.10. IPv6 fails the bindIp unless you set this parameter in the config or as a command line parameter. Here is what I did:

  • Created a VPN in AWS that auto generates IPv6 addresses for a new server.
  • Provisioned a new t2.medium AWS Linux server in the VPC
  • Downloaded and installed mongodb using the yum installation documentation: https://docs.mongodb.com/manual/tutorial/install-mongodb-on-amazon/
  • Added the BindIp and adjusted the /etc/mongod.conf file as follows:

net:
  port: 27017
  bindIp: 2600:1f18:c:da00:767d:4c5f:df1:b32
processManagement:
  fork: "true"
storage:
  dbPath: /data/db
  engine: wiredTiger
  wiredTiger:
    engineConfig:
      cacheSizeGB: 3
systemLog:
  destination: file
  path: /data/db/mongodb.log

  • Tried to run `sudo service mongod start` and received the following error in the log:

2017-02-09T22:23:16.040+0000 I CONTROL  [initandlisten] MongoDB starting : pid=8989 port=27017 dbpath=/data/db 64-bit host=ip-10-0-0-67
2017-02-09T22:23:16.040+0000 I CONTROL  [initandlisten] db version v3.2.10
2017-02-09T22:23:16.040+0000 I CONTROL  [initandlisten] git version: 79d9b3ab5ce20f51c272b4411202710a082d0317
2017-02-09T22:23:16.040+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.0-fips 29 Mar 2010
2017-02-09T22:23:16.040+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2017-02-09T22:23:16.040+0000 I CONTROL  [initandlisten] modules: none
2017-02-09T22:23:16.040+0000 I CONTROL  [initandlisten] build environment:
2017-02-09T22:23:16.040+0000 I CONTROL  [initandlisten]     distmod: amazon
2017-02-09T22:23:16.040+0000 I CONTROL  [initandlisten]     distarch: x86_64
2017-02-09T22:23:16.040+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2017-02-09T22:23:16.040+0000 I CONTROL  [initandlisten] options: { config: "/data/mongod.conf", net: { bindIp: "localhost,dc_1-db_1", port: 27017 }, processManagement: { fork: true }, storage: { dbPath: "/data/db", engine: "wiredTiger", wiredTiger: { engineConfig: { cacheSizeGB: 3 } } }, systemLog: { destination: "file", path: "/data/db/mongodb.log" } }
2017-02-09T22:23:16.108+0000 I NETWORK  [initandlisten] getaddrinfo("dc_1-db_1") failed: Name or service not known
2017-02-09T22:23:16.109+0000 E NETWORK  [initandlisten] listen(): socket is invalid.
2017-02-09T22:23:16.109+0000 E STORAGE  [initandlisten] Failed to set up sockets during startup.
2017-02-09T22:23:16.109+0000 I CONTROL  [initandlisten] dbexit:  rc: 48

  • Then I modified the config file as follows:

net:
  port: 27017
  bindIp: 2600:1f18:c:da00:767d:4c5f:df1:b32
  ipv6: true
processManagement:
  fork: "true"
storage:
  dbPath: /data/db
  engine: wiredTiger
  wiredTiger:
    engineConfig:
      cacheSizeGB: 3
systemLog:
  destination: file
  path: /data/db/mongodb.log

  • Then tried to run `sudo service mongod start` and it started successfully.
  • I then shut it down, removed the config setting for ipv6 and ran the mongod command manually with the `--ipv6` parameter.

Based on the results, there is no evidence that this option has been removed.

Generated at Thu Feb 08 07:59:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.