[SERVER-30086] Fix logging when mongod bound to port 0 Created: 11/Jul/17  Updated: 30/Oct/23  Resolved: 15/Dec/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.5.10
Fix Version/s: 3.7.1

Type: Bug Priority: Minor - P4
Reporter: Ben Shteinfeld Assignee: Billy Donahue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-43432 Remove TODO in transport_layer_asio.cpp Backlog
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platforms 2017-10-23, Platforms 2017-11-13, Platforms 2017-12-04, Platforms 2017-12-18
Participants:

 Description   

Binding mongod to port 0 will bind the process to any available port on the OS, however the logging of mongod outputs that mongod is listening on port 0.



 Comments   
Comment by Githook User [ 15/Dec/17 ]

Author:

{'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}

Message: SERVER-30086 better log message when using --port 0
Branch: master
https://github.com/mongodb/mongo/commit/661bb326d8a02dfa202b003d1766a939e264e2bd

Generated at Thu Feb 08 04:22:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.