[SERVER-29920] restore the "server is now listening on port xxxx" log message Created: 29/Jun/17 Updated: 30/Oct/23 Resolved: 29/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.11 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Eric Milkie | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Platforms 2017-07-10, Platforms 2017-07-31 |
| Participants: |
| Description |
|
It used to say something like "NETWORK [thread1] waiting for connections on port 27017" when startup was complete. |
| Comments |
| Comment by Githook User [ 29/Jul/17 ] | ||
|
Author: {'email': 'acm@mongodb.com', 'username': 'acmorrow', 'name': 'Andrew Morrow'}Message: Also, fix some broken parameter handling for the legacy transport | ||
| Comment by Andrew Morrow (Inactive) [ 25/Jul/17 ] | ||
|
milkie - I don't really see how it could be related. The dbclient networking still flows through the MessagingPort subsystem, which we haven't changed to use ASIO. jbreams please let me know if you disagree and can see a way your recent changes would have led to the observed changes in dbclient. | ||
| Comment by Eric Milkie [ 19/Jul/17 ] | ||
|
Sorry to add on here, but I noticed the following and am wondering if they are all related to the ASIO changes.. dbclient.cpp can now report the following messages: (typically via the shell)
and
Neither of which are ideal. The weirdness is coming from the fact that the errmsg string is being set to literally "failed" with no other context. | ||
| Comment by Andrew Morrow (Inactive) [ 29/Jun/17 ] | ||
|
We will definitely get this addressed. | ||
| Comment by Andy Schwerin [ 29/Jun/17 ] | ||
|
+1 for a log message when the server starts listening. | ||
| Comment by Andrew Morrow (Inactive) [ 29/Jun/17 ] | ||
|
If you start up the server with the legacy transport layer, you will still get that message, but the new on-by-default ASIO based transport layer doesn't issue it. | ||
| Comment by James Wahlin [ 29/Jun/17 ] | ||
|
I believe this is the code that generated this message: https://github.com/mongodb/mongo/blob/943ede3296b190c97fe6ae53f7b718de22cd074d/src/mongo/util/net/listen.cpp#L590 |