Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-1653

SSL handshaking terminates with Secure Renegotiation disabled

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • 3.1.3
    • None
    • Core
    • None
    • Windows NodeJS (8.10.0), driver v3.1.3 connecting to W2012R2 mongod v3.6.7

    Description

      The node driver in replicaset mode with auth and SSL enabled fails to connect resulting in an auth error. From the redacted log snippet below, we see the "encountered a network error during SourceMessage" message, which relates to the issue filed under SERVER-34621 identifying the limitation of renegotiating the TLS handshake on the same connection.

      That said, the log sequence indicates that the monitoring thread and the user thread are using the same connection ID. Leading me to suspect that the connection pool incorrectly being overloaded. This seems antithetical to the SDAM requirements. Would it be possible to let the monitoring thread have it's own dedicated connection?

      2018-08-xxxxx W NETWORK  [connXX] no SSL certificate provided by peer
      2018-08-xxxxx D COMMAND  [connXX] run command admin.$cmd { ismaster: true, client: { driver: { name: "nodejs", version: "3.1.4" }, os: { type: "Windows_NT", name: "win32", architecture: "x64", version: "10.0.14393" }, platform: "Node.js v8.11.4, LE, mongodb-core: 3.1.3" }, compression: [], $readPreference: { mode: "secondaryPreferred" }, $db: "admin" }
      2018-08-xxxxx I NETWORK  [connXX] received client metadata from 192.0.2.1:65000 connXX: { driver: { name: "nodejs", version: "3.1.4" }, os: { type: "Windows_NT", name: "win32", architecture: "x64", version: "10.0.14393" }, platform: "Node.js v8.11.4, LE, mongodb-core: 3.1.3" }
      2018-08-xxxxx D NETWORK  [connXX] Starting server-side compression negotiation
      2018-08-xxxxx D NETWORK  [connXX] No compressors provided
      2018-08-xxxxx I COMMAND  [connXX] command admin.$cmd command: isMaster { ismaster: true, client: { driver: { name: "nodejs", version: "3.1.4" }, os: { type: "Windows_NT", name: "win32", architecture: "x64", version: "10.0.14393" }, platform: "Node.js v8.11.4, LE, mongodb-core: 3.1.3" }, compression: [], $readPreference: { mode: "secondaryPreferred" }, $db: "admin" } numYields:0 reslen:761 locks:{} protocol:op_query 0ms
      2018-08-xxxxx D NETWORK  [connXX] Session from 192.0.2.1:65000 encountered a network error during SourceMessage
      2018-08-xxxxx I NETWORK  [connXX] end connection 192.0.2.1:65000 (19 connections now open)
      

      Attachments

        Issue Links

          Activity

            People

              matt.broadstone@mongodb.com Matt Broadstone
              luke.prochazka@mongodb.com Luke Prochazka
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: