mongodump 100.15.0 breaks with unclear timeout message

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Tools and Replicator
    • 11

      Problem Statement/Rationale

      When connecting to a certain MongoDB instance, version 100.14.1 will take backups without issue, however apparently any tool from mongodb-tools 100.15 (tested: mongodb, mongostat) will fail with the following error message:
      mongostat --host REDACTED --port 27017 --username backup --authenticationDatabase admin --ssl --password REDACTED
      [...]
      failed to connect to mongodb://REDACTED:27017/: server selection error: context deadline exceeded, current topology: { Type: Single, Servers: [

      { Addr: REDACTED:27017, Type: Unknown, Last error: calculated server-side timeout (0 ms) is less than or equal to 0 (): operation not sent to server, as Timeout would be exceeded: context deadline exceeded }

      , ] }

      Steps to Reproduce

      Update to 100.15.0, attempt to connect to a system via TLS.

      Expected Results

      mongostat/mongodump work as expected after the update

      Actual Results

      mongostat/mongodump refuses to connect for no apparent reason with an unclear error message.

      Additional Notes

      This issue does not occur via an insecure connection, it only breaks with --ssl. We suspect this is due to the major version change of the Go Driver in this release, which appears to have changed some internal connection logic, but cannot verify this assumption ourselves.

            Assignee:
            Unassigned
            Reporter:
            providing babiel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: