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

Confusing severity values when mongo shell start fails

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: 2.8.0-rc4
    • Fix Version/s: 3.0.0-rc6
    • Component/s: Logging, Shell
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      start "mongo" without a mongod running.

      Show
      start "mongo" without a mongod running.

      Description

      When I start a mongo shell with 2.8.0-rc4 and no mongod is running, I get the following error:

      $ mongo
      MongoDB shell version: 2.8.0-rc4
      connecting to: test
      2015-01-07T17:56:51.503+1100 W NETWORK  Failed to connect to 127.0.0.1:27017, reason: errno:61 Connection refused
      2015-01-07T17:56:51.504+1100 I QUERY    Error: couldn't connect to server 127.0.0.1:27017 (127.0.0.1), connection attempt failed
          at connect (src/mongo/shell/mongo.js:179:14)
          at (connect):1:6 at src/mongo/shell/mongo.js:179
      exception: connect failed

      The first line has severity W = Warning and the second line has severity I = Information.

      I'd expect both of these to be E = Error, although the first one is debatable, but the second one explicitly says "Error:". Additionally, I'd expect the second line not have the component QUERY, but also NETWORK instead.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: