Uploaded image for project: 'Evergreen'
  1. Evergreen
  2. EVG-1001

process cleanup not catching mongod process on OSX

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: v3
    • Component/s: None
    • Labels:
      None

      Description

      Every 20-30 runs of an Evergreen self-test task on our OSX variants, we have a failure where our database does not appear to come up. On further inspection, it looks like what's happening is:

      1. There is an existing mongod process from a previous self-test task
      2. Our new mongod process fails to spin up due to port contention
      3. The check for a running mongod succeeds, since the old mongod is up
      4. The old mongod shuts down at some point, leaving our tests high and dry

      An example of this is https://evergreen.mongodb.com/task/mci_osx_ui_e50c54c4f4796b96705f15074bf65ca0fab49343_16_05_06_18_33_05#/log/S

      Note the "mongod" present in the system logs at task start.

        Attachments

          Activity

            People

            Assignee:
            mpobrien Michael O'Brien
            Reporter:
            kyle.erf Kyle Erf
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: