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

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Security
    • Labels:
      None
    • ALL
    • 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
    • Security 2019-05-20, Service Arch 2019-06-17, Service Arch 2019-07-01

      CC mark.benvenuto + jeff.yemin
      See repro steps.

            Assignee:
            mira.carey@mongodb.com Mira Carey
            Reporter:
            kevin.albertson@mongodb.com Kevin Albertson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: