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

Segmentation fault in mongos at shutdown due to unconstructed ClientCursorManager

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: 3.2.10
    • Fix Version/s: 3.2.11
    • Component/s: Sharding
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Completed:
    • Steps To Reproduce:
      Hide

      Start mongos with unresolvable hostname as configdb parameter. I.e.:

      mongos --configdb asdf

      After 10 attempts to resolve the name of the host, it dies with segfault.

      Show
      Start mongos with unresolvable hostname as configdb parameter. I.e.: mongos --configdb asdf After 10 attempts to resolve the name of the host, it dies with segfault.
    • Sprint:
      Sharding 2016-11-21

      Description

      When mongos has been started with invalid hostname as a configdb value, it dies with Segmentation fault:

      E SHARDING [mongosMain] uncaught DBException in mongos main: 7 unable to resolve DNS for host adsf
      F - [mongosMain] Invalid access at address: 0x18
      F - [mongosMain] Got signal: 11 (Segmentation fault).

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: