Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-68548

mongo shell version 4.4.15 logging asio message despite --quiet flag

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • v6.1, v6.0, v5.0, v4.4
    • Security 2022-08-22, Security 2022-09-05

    Description

      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

      Attachments

        Activity

          People

            adam.rayner@mongodb.com Adam Rayner
            vincent.do@mongodb.com Vincent Do
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: