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

Unable to connect remote client on GCP

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Community Answered
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.2.1
    • Component/s: Networking
    • Labels:
      None
    • Server Triage
    • Fully Compatible
    • ALL
    • Hide

      Connect thought mongo client utility or MongoDB Atlas remotely on standalone instance deployed on GCP VM. We were facing similar issue in MongoDB Atlas instance on GCP also.

       

      It seems the instance is resetting the connection, we are able to telnet the port remotely. Now open allow all in the firewall rules as well as on iptables for the underlying service.

      Show
      Connect thought mongo client utility or MongoDB Atlas remotely on standalone instance deployed on GCP VM. We were facing similar issue in MongoDB Atlas instance on GCP also.   It seems the instance is resetting the connection, we are able to telnet the port remotely. Now open allow all in the firewall rules as well as on iptables for the underlying service.

      We are getting the following error intermittently after verifying the server logs. It sometimes connect through atlas but have to click refresh data continuously.

      2019-12-03T16:01:16.362+0000 I  ACCESS   [conn61] Successfully authenticated as principal ncr_service on pwm from client 104.129.196.84:361992019-12-03T16:01:45.442+0000 I  NETWORK  [conn61] end connection 104.129.196.84:36199 (2 connections now open)2019-12-03T16:01:46.681+0000 I  NETWORK  [listener] connection accepted from 104.129.196.84:34043 #62 (3 connections now open)2019-12-03T16:01:46.879+0000 I  NETWORK  [conn62] received client metadata from 104.129.196.84:34043 conn62: { driver: { name: "nodejs-core", version: "3.2.7" }, os: { type: "Windows_NT", name: "win32", architecture: "x64", version: "10.0.17134" }, platform: "Node.js v10.2.0, LE", application: { name: "MongoDB Compass Community" } }2019-12-03T16:01:47.589+0000 I  ACCESS   [conn62] Successfully authenticated as principal ncr_service on pwm from client 104.129.196.84:340432019-12-03T16:02:16.668+0000 I  NETWORK  [conn62] end connection 104.129.196.84:34043 (2 connections now open)2019-12-03T16:02:17.909+0000 I  NETWORK  [listener] connection accepted from 104.129.196.84:1397 #63 (3 connections now open)2019-12-03T16:02:18.109+0000 I  NETWORK  [conn63] received client metadata from 104.129.196.84:1397 conn63: { driver: { name: "nodejs-core", version: "3.2.7" }, os: { type: "Windows_NT", name: "win32", architecture: "x64", version: "10.0.17134" }, platform: "Node.js v10.2.0, LE", application: { name: "MongoDB Compass Community" } }2019-12-03T16:02:18.827+0000 I  ACCESS   [conn63] Successfully authenticated as principal ncr_service on pwm from client 104.129.196.84:13972019-12-03T16:02:47.900+0000 I  NETWORK  [conn63] end connection 104.129.196.84:1397 (2 connections now open)

            Assignee:
            backlog-server-triage [HELP ONLY] Backlog - Triage Team
            Reporter:
            vishal.deore@techgeek.co.in Vishal Deore
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: