Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-38127

BindIp option does not work correctly in a config file when moving from 3.6.2 to 3.6.8

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • ALL

      Hi,

      I was using 3.6.2 and the attached configuration file worked correctly.

      When moving to 3.6.8 it no longer works - I get the following error:

      2018-11-14T14:19:03.839+0000 I CONTROL [initandlisten] target_arch: x86_64
      2018-11-14T14:19:03.839+0000 I CONTROL [initandlisten] options: \{ config: "C:\Program Files\MongoDB\Server\3.6\bin\mongod.cfg", net: { bindIp: "192.168.45.107,192.168.45.106", port: 27057 }, replication: \{ replSetName: "MAP" }, security: \{ authorization: "enabled", keyFile: "C:\Program Files\MongoDB\Server\3.6\bin\keyfile" }, service: true, storage: \{ dbPath: "D:\MongoData\DB", engine: "wiredTiger", wiredTiger: { engineConfig: { cacheSizeGB: 4.0 } } }, systemLog: \{ destination: "file", path: "D:\MongoData\Log\mongod.log" } }
      2018-11-14T14:19:03.841+0000 E STORAGE [initandlisten] Failed to set up listener: SocketException: The requested address is not valid in its context.
      2018-11-14T14:19:03.842+0000 I CONTROL [serviceStopWorker] now exiting
      

      Has the way that the IP address list has to be specified changed at all?

      Thanks

      Ian

      mongod.cfg

            Assignee:
            daniel.hatcher@mongodb.com Danny Hatcher (Inactive)
            Reporter:
            Sputink1969 Ian Hannah [X]
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: