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

Error message for missing config file is misleading

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 4.9.0
    • Affects Version/s: 5.0 Desired
    • Component/s: None
    • Fully Compatible
    • ALL
    • Hide

      Start mongod using a fictitious config file:

      1. /usr/local/bin/mongod -f /etc/not-the-correct-name.conf

      Expected:
      'File: /etc/not-the-correct-name.conf not found'

      Actual:
      Error opening config file: Is a directory
      try '/usr/local/bin/mongod --help' for more information

      Show
      Start mongod using a fictitious config file: /usr/local/bin/mongod -f /etc/not-the-correct-name.conf Expected: 'File: /etc/not-the-correct-name.conf not found' Actual: Error opening config file: Is a directory try '/usr/local/bin/mongod --help' for more information
    • Repl 2020-11-30

      The error message when a user supplies the wrong path information for the configuration file is misleading. It should say something like 'File not found' instead it misidentifies the missing file as a directory and directs the user to --help for further information.

      1. /usr/local/bin/mongod -f /etc/not-the-correct-name.conf
        Error opening config file: Is a directory
        try '/usr/local/bin/mongod --help' for more information

            Assignee:
            varun.ravichandran@mongodb.com Varun Ravichandran
            Reporter:
            dave.cuthbert@mongodb.com Dave Cuthbert (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: