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

mongo --quiet does not silence initial connection messages

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • 3.6.3
    • None
    • Shell
    • None
    • ALL

    Description

      When using the --quiet option, the mongo shell still writes initial connection messages to stdout, when connecting via a replica set URL. These messages should be completely suppressed when the --quiet option is used, and even when they are not suppressed, they should be written to stderr rather than stdout.

      $ mongo --quiet "mongodb://localhost:27017/?replicaSet=rsx" --eval "print('test')"
      2018-02-28T20:52:31.450+0000 I NETWORK  [thread1] Starting new replica set monitor for rsx/localhost:27017
      2018-02-28T20:52:31.451+0000 I NETWORK  [thread1] Successfully connected to localhost:27017 (1 connections now open to localhost:27017 with a 5 second timeout)
      2018-02-28T20:52:31.451+0000 I NETWORK  [thread1] changing hosts to rsx/amz-play:27017 from rsx/localhost:27017
      2018-02-28T20:52:31.451+0000 I NETWORK  [thread1] Successfully connected to amz-play:27017 (1 connections now open to amz-play:27017 with a 5 second timeout)
      test
      

      Attachments

        Issue Links

          Activity

            People

              backlog-server-platform DO NOT USE - Backlog - Platform Team
              andre.spiegel@mongodb.com Andre Spiegel
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: