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

sockets are opened prior to checking for lock file

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • 3.3.1
    • None
    • Networking
    • Fully Compatible
    • ALL
    • v3.2
    • Integration F (02/01/16)
    • 0

    Description

      We used to check for the lock file before opening sockets. This produced a better error message when inadvertently starting two copies of mongod pointing to the same dbpath and using the same ports.
      The bind error message isn't as obvious because we don't know what process is sharing the port; with the lock file, at least we know that mongod is conflicting with another mongod.

      Attachments

        Activity

          People

            adam.midvidy Adam Midvidy
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: