...
I upgraded my mongo 4.4 installation to 4.4.15 today and noticed that the shell logged the following when I'm trying to run a script with the --quiet option: /Users/vincent.do/bin/mongo mongodb://db-dev-aarch64-4.us-east-1.aws.cloud-dev.10gen.cc:27298,db-dev-aarch64-5.us-east-1.aws.cloud-dev.10gen.cc:27298,db-dev-aarch64-6.us-east-1.aws.cloud-dev.10gen.cc:27298/ --tls --quiet --tlsCAFile /Users/vincent.do/cas/ca-mongodb-signatory.pem {"t":{"$date":"2022-08-03T19:50:44.128Z"},"s":"I", "c":"NETWORK", "id":5490002, "ctx":"thread1","msg":"Started a new thread for the timer service"} MongoDB Enterprise mongos> The same behavior is not observed when I use shell version 4.4.10 /Users/vincent.do/bin/mongo mongodb://db-dev-aarch64-4.us-east-1.aws.cloud-dev.10gen.cc:27298,db-dev-aarch64-5.us-east-1.aws.cloud-dev.10gen.cc:27298,db-dev-aarch64-6.us-east-1.aws.cloud-dev.10gen.cc:27298/ --tls --quiet --tlsCAFile /Users/vincent.do/cas/ca-mongodb-signatory.pem MongoDB Enterprise mongos> While this seems like a trivial bug, this might have a pretty big impact for users who rely on the previous behavior of --quiet for operational scripts. (MongoDB Cloud being one of them). FWIW, I was connecting to a 4.4.13 sharded cluster
xgen-internal-githook commented on Wed, 4 Oct 2023 23:39:50 +0000: Author: {'name': 'Adam Rayner', 'email': 'adam.rayner@gmail.com', 'username': ''} Message: SERVER-68548: check quiet globalServerParam before logging Branch: v5.0 https://github.com/mongodb/mongo/commit/b87ca174b4807d0c5cb31c8347deb6877260badb xgen-internal-githook commented on Fri, 16 Sep 2022 14:48:57 +0000: Author: {'name': 'Adam Rayner', 'email': 'adam.rayner@gmail.com'} Message: SERVER-68548: Backport - check quiet globalServerParam before logging Branch: v6.0 https://github.com/mongodb/mongo/commit/f7f6c6928320873089b443da007de119b926f605 xgen-internal-githook commented on Thu, 15 Sep 2022 21:44:36 +0000: Author: {'name': 'Adam Rayner', 'email': 'adam.rayner@gmail.com'} Message: SERVER-68548: check quiet globalServerParam before logging Branch: v4.4 https://github.com/mongodb/mongo/commit/cfe4fe45d31644ff6bfda613169245c7f9a7e2e9 JIRAUSER1262924 commented on Wed, 24 Aug 2022 16:59:00 +0000: This appears to be a side effect from a backported bug fix. I have pushed an additional fix to master and requested backports for all versions going back to 4.4. JIRAUSER1270861 commented on Wed, 24 Aug 2022 09:27:12 +0000: Hi, I'm having the same issue using puppet-mongodb script with --quiet. I'm getting /bin/mongo admin --quiet --host xx:27017 --tls --tlsCertificateKeyFile /etc/ssl/mongodb.pem --tlsCAFile /etc/pki/tls/certs/mgdb-ca.crt --eval "load('/root/.mongorc.js'); db.version()" {"t":{"$date":"2022-08-24T08:21:53.586Z"},"s":"I", "c":"NETWORK", "id":5490002, "ctx":"thread1","msg":"Started a new thread for the timer service"} 4.4.15 instead of only db.version 4.4.15 and that causes an issue on all ours mongdb nodes. JIRAUSER1265262 commented on Thu, 4 Aug 2022 01:41:34 +0000: Forwarding this to the Security team since they have ownership of logging.