[SERVER-50138] Server logs a warning: "No TransportLayer configured during NetworkInterface startup" for each bound socket Created: 06/Aug/20  Updated: 29/Oct/23  Resolved: 10/Jun/21

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: 4.4.0
Fix Version/s: 5.1.0-rc0, 4.4.16

Type: Bug Priority: Minor - P4
Reporter: Radosław Piliszek Assignee: Alex Li
Resolution: Fixed Votes: 0
Labels: neweng, sa-groomed, save-for-alex
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-46724 Provide NetworkInterfaceNoop for pool... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Steps To Reproduce:

Run server and observe the logs.

Sprint: Service Arch 2021-06-14
Participants:
Story Points: 2

 Description   

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. 



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 10/Jun/21 ]

Author:

{'name': 'Alex Li', 'email': 'alex.li@mongodb.com'}

Message: SERVER-50138 Avoid logging no TransportLayer configured in production
Branch: master
https://github.com/mongodb/mongo/commit/57d8a426a83bcf7730fd88ee429e7f8509144fed

Comment by Benjamin Caimano (Inactive) [ 30/Nov/20 ]

radoslaw.piliszek@gmail.com, I agree that a WARNING message is not appropriate in this case. We will be suppressing that message in non-test deployments, it has no impact on the operation of MongoDB processes.

Generated at Thu Feb 08 05:21:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.