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

Server logs a warning: "No TransportLayer configured during NetworkInterface startup" for each bound socket

    • Fully Compatible
    • ALL
    • v4.4
    • Hide

      Run server and observe the logs.

      Show
      Run server and observe the logs.
    • Service Arch 2021-06-14
    • 2

      Each time server binds a socket for listening, it raises the following in logs:

      {
        "t": {"$date":"2020-08-06T14:50:19.281+02:00"},
        "s":"W",
        "c":"ASIO",
        "id":22601,
        "ctx":"main",
        "msg":"No TransportLayer configured during NetworkInterface startup"
      }
      

      I traced it down to here which says "mostly for unittests". The message is confusing, yet seems to be very common when tried in a G search. Stack Overflow also has a question about it here.

      There seems to be no effect on operations whatsoever. It seems to be happening on different platforms. I expect not to see "warnings" on a healthy service, especially ones I seem unable to do anything about.

      Acceptance criteria: This log line doesn't show up in production environments. 

            Assignee:
            alex.li@mongodb.com Alex Li
            Reporter:
            radoslaw.piliszek@gmail.com Radosław Piliszek
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: