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

mongocryptd should not delete existing domain socket if it fails to start TCP socket

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Security
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide
      • start mongocryptd
      • verify you can connect with mongo mongodb://%2Ftmp%2Fmongocryptd.sock/
      • cd to another directory (so pid file differs)
      • start mongocryptd again, which will fail with "SocketException: Address already in use"
      • although other mongocryptd is still running, mongo mongodb://%2Ftmp%2Fmongocryptd.sock/ fails with Connection refused
      Show
      start mongocryptd verify you can connect with mongo mongodb://%2Ftmp%2Fmongocryptd.sock/ cd to another directory (so pid file differs) start mongocryptd again, which will fail with "SocketException: Address already in use" although other mongocryptd is still running, mongo mongodb://%2Ftmp%2Fmongocryptd.sock/ fails with Connection refused
    • Sprint:
      Security 2019-05-20, Service Arch 2019-06-17, Service Arch 2019-07-01

      Description

      CC Mark Benvenuto + Jeffrey Yemin
      See repro steps.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jason.carey Jason Carey
              Reporter:
              kevin.albertson Kevin Albertson
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: