Loading...
Loading...
I just upgraded my Sharded cluster to version 5.0.3. Sometime when I connect to mongos then I get this information message: { "t": { "$date": "2021-10-08T08:02:49.206Z" }, "s": "I", "c": "NETWORK", "id": 4915701, "ctx": "-", "msg": "Initialized wire specification", "attr": { "spec": { "incomingExternalClient": { "minWireVersion": 0, "maxWireVersion": 13 }, "incomingInternalClient": { "minWireVersion": 0, "maxWireVersion": 13 }, "outgoing": { "minWireVersion": 0, "maxWireVersion": 13 }, "isInternalClient": false } } } For me this is a problem, because the mongo script runs as automatic job and a non-emtpy return value is considered as an error. Apart from that, it is annoying for the user. Is the a solution to get rid of this message?
xgen-internal-githook commented on Tue, 13 Sep 2022 19:26:54 +0000: Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'} Message: SERVER-60551 Fix mongo (shell) initializer stages (cherry picked from commit 72344e39acd0f26a3b72a68520edde77483e69c9) Branch: v6.0 https://github.com/mongodb/mongo/commit/1451ddccfc4d24b3686a4851d17c82cbf3d7f35b xgen-internal-githook commented on Mon, 12 Sep 2022 22:04:43 +0000: Author: {'name': 'Ryan Egesdahl', 'email': 'ryan.egesdahl@mongodb.com', 'username': 'deriamis'} Message: SERVER-60551 Fix mongo (shell) initializer stages Branch: master https://github.com/mongodb/mongo/commit/72344e39acd0f26a3b72a68520edde77483e69c9 msmith@mindbridge.ai commented on Sun, 3 Apr 2022 14:48:23 +0000: This still occurs in mongo 5.0.6, and we did not encounter it in 3.x or 4.x. We have a monitoring script that runs every couple of minutes to check: mongo -u ... -p ... --authenticationDatabase admin --quiet --eval 'rs.status().myState' This should return "1", but occasionally outputs something like: {"t":{"$date":"2022-04-03T14:30:06.329Z"},"s":"I", "c":"NETWORK", "id":4915701, "ctx":"-","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":13},"outgoing":{"minWireVersion":0,"maxWireVersion":13},"isInternalClient":false}}} 1 I can reproduce it by running it a couple hundred times or less in a loop. I thought about trying mongosh, but the long startup time makes me think it's not intended for scripted use: $ time mongo -u ... -p ... --authenticationDatabase admin --quiet --eval 'rs.status().myState' 1 real 0m0.107s user 0m0.091s sys 0m0.015s time mongosh -u ... -p ... --authenticationDatabase admin --quiet --eval 'rs.status().myState' 1 real 0m3.925s user 0m2.888s sys 0m0.164s brooke.miller commented on Tue, 2 Nov 2021 15:03:22 +0000: We've re-assigned this to the Shell Team to get feedback on the appropriate next steps here. ratika.gandhi commented on Mon, 25 Oct 2021 17:40:39 +0000: Passing it to STM because they own the epic for maintaining the old shell. eric.sedor commented on Wed, 20 Oct 2021 18:27:38 +0000: Thanks wernfried.domscheit@sunrise.net, I can reproduce this using the following (with a 5.0.3 mongos running on port 27017): bash-3.2$ touch noop.js bash-3.2$ mongo noop.js MongoDB shell version v5.0.3 connecting to: mongodb://127.0.0.1:27017/?compressors=disabled&gssapiServiceName=mongodb Implicit session: session { "id" : UUID("dd90f39a-4bbe-4e8f-b07d-c752773b066c") } MongoDB server version: 5.0.3 bash-3.2$ for i in {1..100}; do mongo --quiet noop.js;done {"t":{"$date":"2021-10-20T18:20:14.538Z"},"s":"I", "c":"NETWORK", "id":4915701, "ctx":"-","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":13},"outgoing":{"minWireVersion":0,"maxWireVersion":13},"isInternalClient":false}}} {"t":{"$date":"2021-10-20T18:20:25.866Z"},"s":"I", "c":"NETWORK", "id":4915701, "ctx":"-","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":13},"incomingInternalClient":{"minWireVersion":0,"maxWireVersion":13},"outgoing":{"minWireVersion":0,"maxWireVersion":13},"isInternalClient":false}}} bash-3.2$ This seems to occur a few times out of 100 on 5.0.3, but not at all on 4.4.9 This seems related to SERVER-46636 or could be a subset of SERVER-3492, but I am not yet certain. JIRAUSER1257089 commented on Tue, 19 Oct 2021 06:08:21 +0000: The message appears directly when it connects to the MongoDB, before any command is executed. eric.sedor commented on Mon, 18 Oct 2021 17:29:22 +0000: Thanks wernfried.domscheit@sunrise.net, First, mongosh is under active development and is significantly more likely to receive bug fixes and improvements. Whereas the mongo shell is deprecated. I'd recommend starting to make use of mongosh as soon as you reasonably can. That said, I'm not able to readily reproduce seeing that message on connection in the mongo shell version 5.0.3. Possibly it is a result of something within the script you're running. Are you able to identify a command within your script that is producing that output? JIRAUSER1257089 commented on Thu, 14 Oct 2021 06:35:31 +0000: Hi Eric Yes, I run a script in classic mongo shell, the message is printed on standard output. The new mongosh is not working, so it is no option to use it. MongoDB shell version v5.0.3 MongoDB server version: 5.0.3 Wernfried eric.sedor commented on Tue, 12 Oct 2021 22:41:46 +0000: Hi wernfried.domscheit@sunrise.net, it sounds like from your description of a script that you are using either the mongo or mongosh shell, is that right? And that this message is being thrown into the output of that script? Can you clarify which shell and which shell version you're seeing this message on? Eric
Not reproducible, happens only occasionally.
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.