Operational Defect Database

BugZero found this defect 2433 days ago.

MongoDB | 399238

[SERVER-29920] restore the "server is now listening on port xxxx" log message

Last update date:


Affected products:

MongoDB Server

Affected releases:

No affected releases provided.

Fixed releases:




It used to say something like "NETWORK [thread1] waiting for connections on port 27017" when startup was complete.

Top User Comments

xgen-internal-githook commented on Sat, 29 Jul 2017 13:31:54 +0000: Author: {'email': 'acm@mongodb.com', 'username': 'acmorrow', 'name': 'Andrew Morrow'} Message: SERVER-29920 Restore missing message once listening Also, fix some broken parameter handling for the legacy transport Branch: master https://github.com/mongodb/mongo/commit/a402b45dfb18951a2c0de17d52e2f8dabc01b5d2 acm commented on Tue, 25 Jul 2017 18:48:14 +0000: 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. milkie commented on Wed, 19 Jul 2017 12:50:19 +0000: 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) [js_test:change_notification] 2017-07-19T08:45:58.250-0400 2017-07-19T08:45:58.250-0400 I NETWORK [thread1] reconnect ( failed failed and [js_test:change_notification] 2017-07-19T08:45:58.378-0400 2017-07-19T08:45:58.378-0400 I NETWORK [thread1] trying reconnect to ( failed 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. acm commented on Thu, 29 Jun 2017 14:07:37 +0000: We will definitely get this addressed. schwerin commented on Thu, 29 Jun 2017 13:49:17 +0000: +1 for a log message when the server starts listening. acm commented on Thu, 29 Jun 2017 13:38:31 +0000: 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. james.wahlin@10gen.com commented on Thu, 29 Jun 2017 13:24:22 +0000: I believe this is the code that generated this message: https://github.com/mongodb/mongo/blob/943ede3296b190c97fe6ae53f7b718de22cd074d/src/mongo/util/net/listen.cpp#L590

Additional Resources / Links


BugZero Risk Score

Coming soon



Have you been affected by this bug?


Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.


Login to read and write comments.

Have you ever...

had your data corrupted from a