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

Connection closures are not logged when server shuts down

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 4.3.6
    • Component/s: Logging, Networking
    • None
    • Service Arch
    • ALL
      • Connect to mongod from the client
      • Shut down mongod
      • Review mongod log for the connection

      When a client connects to the server and subsequently disconnects, the mongod log includes line items showing the connection being established and closed:

      {"t":{"$date":"2020-04-13T20:42:42.167-04:00"},"s":"I", "c":"NETWORK", "id":51800,  "ctx":"conn59","msg":"client metadata","attr":{"remote":"127.0.0.1:54986","client":"conn59","doc":{"driver":{"name":"mongo-ruby-driver","version":"2.11.
      4"},"os":{"type":"linux","name":"linux-gnu","architecture":"x86_64"},"platform":"2.7.0, x86_64-linux, x86_64-pc-linux-gnu"}}}
      {"t":{"$date":"2020-04-13T20:42:54.572-04:00"},"s":"I", "c":"NETWORK", "id":22944,  "ctx":"conn59","msg":"connection ended","attr":{"remote":"127.0.0.1:54986","connectionCount":9}}
      

      When a client connects to the server and the server shuts down (I used shutdown:1 command), it appears that the server is not creating a corresponding log entry for the connections being closed.

      For example, in https://gist.github.com/p-mongo/a6976d218e2eb1140b1bac0f95415306 there is no log entry for closing conn136.

      I expected the server to log all connection closures, whether those are initiated by the client or the server.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            oleg.pudeyev@mongodb.com Oleg Pudeyev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: