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

Windows 4.2 mongo shell cannot connect to a 4.2 Cluster

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.2.0-rc3
    • None
    • None
    • Major Change
    • ALL
    • Storage Engines 2019-07-29

    Description

      Currently cannot connect from a 4.2.0-rc2 Windows shell to a 4.2 Atlas cluster.

      When testing from a 4.0.10 Windows shell to a 4.2.0-rc1 Atlas cluster:

      MongoDB shell version v4.0.10
      		 
      Enter password:
      		 
      connecting to: mongodb://42betatest-shard-00-00-dgtt4.gcp.mongodb.net.:27017,42betatest-shard-00-01-dgtt4.gcp.mongodb.net.:27017,42betatest-shard-00-02-dgtt4.gcp.mongodb.net.:27017/test?authSource=admin&gssapiServiceName=mongodb&replicaSet=42BetaTest-shard-0&ssl=true
      		 
      2019-07-02T13:24:07.928-0400 I NETWORK  [js] Starting new replica set monitor for 42BetaTest-shard-0/42betatest-shard-00-00-dgtt4.gcp.mongodb.net.:27017,42betatest-shard-00-01-dgtt4.gcp.mongodb.net.:27017,42betatest-shard-00-02-dgtt4.gcp.mongodb.net.:27017
      		 
      2019-07-02T13:24:08.056-0400 I NETWORK  [ReplicaSetMonitor-TaskExecutor] Successfully connected to 42betatest-shard-00-01-dgtt4.gcp.mongodb.net.:27017 (1 connections now open to 42betatest-shard-00-01-dgtt4.gcp.mongodb.net.:27017 with a 5 second timeout)
      		 
      2019-07-02T13:24:08.056-0400 I NETWORK  [js] Successfully connected to 42betatest-shard-00-00-dgtt4.gcp.mongodb.net.:27017 (1 connections now open to 42betatest-shard-00-00-dgtt4.gcp.mongodb.net.:27017 with a 5 second timeout)
      		 
      2019-07-02T13:24:08.083-0400 I NETWORK  [js] changing hosts to 42BetaTest-shard-0/42betatest-shard-00-00-dgtt4.gcp.mongodb.net:27017,42betatest-shard-00-01-dgtt4.gcp.mongodb.net:27017,42betatest-shard-00-02-dgtt4.gcp.mongodb.net:27017 from 42BetaTest-shard-0/42betatest-shard-00-00-dgtt4.gcp.mongodb.net.:27017,42betatest-shard-00-01-dgtt4.gcp.mongodb.net.:27017,42betatest-shard-00-02-dgtt4.gcp.mongodb.net.:27017
      		 
      2019-07-02T13:24:08.198-0400 I NETWORK  [ReplicaSetMonitor-TaskExecutor] Successfully connected to 42betatest-shard-00-00-dgtt4.gcp.mongodb.net:27017 (1 connections now open to 42betatest-shard-00-00-dgtt4.gcp.mongodb.net:27017 with a 5 second timeout)
      		 
      2019-07-02T13:24:08.198-0400 I NETWORK  [js] Successfully connected to 42betatest-shard-00-01-dgtt4.gcp.mongodb.net:27017 (1 connections now open to 42betatest-shard-00-01-dgtt4.gcp.mongodb.net:27017 with a 5 second timeout)
      		 
      2019-07-02T13:24:08.344-0400 I NETWORK  [ReplicaSetMonitor-TaskExecutor] Successfully connected to 42betatest-shard-00-02-dgtt4.gcp.mongodb.net:27017 (1 connections now open to 42betatest-shard-00-02-dgtt4.gcp.mongodb.net:27017 with a 5 second timeout)
      		 
      Implicit session: session { "id" : UUID("e5c3291d-b04b-4646-ab33-04085a8436ed") }
      		 
      MongoDB server version: 4.2.0-rc1
      		 
      WARNING: shell and server versions do not match
      		 
      MongoDB Enterprise 42BetaTest-shard-0:PRIMARY>

      When testing from a 4.2.0-rc2 Windows shell to a 4.2.0-rc1 Atlas cluster:

      MongoDB shell version v4.2.0-rc2
      		 
      Enter password:
      		 
      connecting to: mongodb://42betatest-shard-00-01-dgtt4.gcp.mongodb.net:27017,42betatest-shard-00-02-dgtt4.gcp.mongodb.net:27017,42betatest-shard-00-00-dgtt4.gcp.mongodb.net:27017/test?authSource=admin&compressors=disabled&gssapiServiceName=mongodb&replicaSet=42BetaTest-shard-0&ssl=true
      		 
      2019-07-02T13:26:01.810-0400 I  NETWORK  [js] Starting new replica set monitor for 42BetaTest-shard-0/42betatest-shard-00-01-dgtt4.gcp.mongodb.net:27017,42betatest-shard-00-02-dgtt4.gcp.mongodb.net:27017,42betatest-shard-00-00-dgtt4.gcp.mongodb.net:27017
      		 
      2019-07-02T13:26:01.811-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to 42betatest-shard-00-00-dgtt4.gcp.mongodb.net:27017
      		 
      2019-07-02T13:26:01.811-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to 42betatest-shard-00-02-dgtt4.gcp.mongodb.net:27017
      		 
      2019-07-02T13:26:01.811-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to 42betatest-shard-00-01-dgtt4.gcp.mongodb.net:27017
      		 
      2019-07-02T13:26:02.024-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Ending connection to host 42betatest-shard-00-00-dgtt4.gcp.mongodb.net:27017 due to bad connection status: HostUnreachable: Connection closed by peer; 0 connections to that host remain open
      		 
      2019-07-02T13:26:02.029-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Ending connection to host 42betatest-shard-00-02-dgtt4.gcp.mongodb.net:27017 due to bad connection status: HostUnreachable: Connection closed by peer; 0 connections to that host remain open
      		 
      2019-07-02T13:26:02.050-0400 W  NETWORK  [ReplicaSetMonitor-TaskExecutor] Unable to reach primary for set 42BetaTest-shard-0
      		 
      2019-07-02T13:26:02.051-0400 I  NETWORK  [ReplicaSetMonitor-TaskExecutor] Cannot reach any nodes for set 42BetaTest-shard-0. Please check network connectivity and the status of the set. This has happened for 1 checks in a row.
      		 
      2019-07-02T13:26:02.052-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Ending connection to host 42betatest-shard-00-01-dgtt4.gcp.mongodb.net:27017 due to bad connection status: HostUnreachable: Connection closed by peer; 0 connections to that host remain open
      		 
      2019-07-02T13:26:02.338-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Ending connection to host 42betatest-shard-00-00-dgtt4.gcp.mongodb.net:27017 due to bad connection status: HostUnreachable: Connection closed by peer; 0 connections to that host remain open
      		 
      2019-07-02T13:26:02.339-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Ending connection to host 42betatest-shard-00-01-dgtt4.gcp.mongodb.net:27017 due to bad connection status: HostUnreachable: Connection closed by peer; 0 connections to that host remain open
      		 
      2019-07-02T13:26:02.340-0400 W  NETWORK  [ReplicaSetMonitor-TaskExecutor] Unable to reach primary for set 42BetaTest-shard-0
      		 
      2019-07-02T13:26:02.340-0400 I  NETWORK  [ReplicaSetMonitor-TaskExecutor] Cannot reach any nodes for set 42BetaTest-shard-0. Please check network connectivity and the status of the set. This has happened for 2 checks in a row.
      		 
      2019-07-02T13:26:02.340-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Ending connection to host 42betatest-shard-00-02-dgtt4.gcp.mongodb.net:27017 due to bad connection status: HostUnreachable: Connection closed by peer; 0 connections to that host remain open
      		 
      2019-07-02T13:26:02.843-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Ending connection to host 42betatest-shard-00-00-dgtt4.gcp.mongodb.net:27017 due to bad connection status: HostUnreachable: Connection closed by peer; 0 connections to that host remain open

      The above will loop indefinitely. To verify the 4.2.0-rc2 shell could still connect to non-4.2 servers I also tested connecting to a 3.6.13 Atlas cluster:

      MongoDB shell version v4.2.0-rc2
      		 
      Enter password:
      		 
      connecting to: mongodb://m10-dev-shard-00-02-dgtt4.mongodb.net:27017,m10-dev-shard-00-00-dgtt4.mongodb.net:27017,m10-dev-shard-00-01-dgtt4.mongodb.net:27017/test?authSource=admin&compressors=disabled&gssapiServiceName=mongodb&replicaSet=m10-dev-shard-0&ssl=true
      		 
      2019-07-02T13:30:34.669-0400 I  NETWORK  [js] Starting new replica set monitor for m10-dev-shard-0/m10-dev-shard-00-02-dgtt4.mongodb.net:27017,m10-dev-shard-00-00-dgtt4.mongodb.net:27017,m10-dev-shard-00-01-dgtt4.mongodb.net:27017
      		 
      2019-07-02T13:30:34.670-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to m10-dev-shard-00-02-dgtt4.mongodb.net:27017
      		 
      2019-07-02T13:30:34.670-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to m10-dev-shard-00-00-dgtt4.mongodb.net:27017
      		 
      2019-07-02T13:30:34.670-0400 I  CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to m10-dev-shard-00-01-dgtt4.mongodb.net:27017
      		 
      2019-07-02T13:30:35.433-0400 I  NETWORK  [ReplicaSetMonitor-TaskExecutor] Confirmed replica set for m10-dev-shard-0 is m10-dev-shard-0/m10-dev-shard-00-00-dgtt4.mongodb.net:27017,m10-dev-shard-00-01-dgtt4.mongodb.net:27017,m10-dev-shard-00-02-dgtt4.mongodb.net:27017
      		 
      Implicit session: session { "id" : UUID("08d396c6-ce2d-4f4c-80a2-60c47f325dc9") }
      		 
      MongoDB server version: 3.6.13
      		 
      WARNING: shell and server versions do not match
      		 
      MongoDB Enterprise m10-dev-shard-0:PRIMARY>

      My OS Details are as follows:

      systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
      		 
      OS Name:                   Microsoft Windows 10 Pro
      		 
      OS Version:                10.0.17763 N/A Build 17763

      Attachments

        Issue Links

          depends on

          Bug - A problem which impairs or prevents the functions of the product. WT-4913 Fix the Windows CRC32 on blocks that aren't 8B aligned and/or multiples of 8B

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Task - A task that needs to be done. DOCS-12883 4.2 downgrade to 4.0 on windows will require a specific min 4.0.x version

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-storage-engines Backlog - Storage Engines Team
              alex.bevilacqua@mongodb.com Alex Bevilacqua
              Votes:
              0 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: