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

Error/log information is printed to standard output

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Works as Designed
    • Affects Version/s: 4.1.13
    • Fix Version/s: None
    • Component/s: Logging
    • Labels:
      None
    • Operating System:
      ALL

      Description

      I tried running mongo-orchestration's test suite, and in the process of that mongod died with an error message while not writing anything to its log file. The error output was sent to standard output stream, whereas I expected to find error output in the standard error stream.

      This is the config I used, saved as /tmp/c:

      nojournal=true
      configsvr=true
      dbpath=/tmp/mongo-A_fAH5
      logpath=/tmp/mongo-A_fAH5/mongod.log
      

      speed% /usr/local/m/versions/4.1/mongod --config /tmp/c --port 1027            
      2019-06-10T20:44:21.454-0400 F  CONTROL  [main] Failed global initialization: BadValue: nojournal is not allowed when configsvr is specified
      

      At the end of this execution, /tmp/mongo-A_fAH5/mongod.log did not exist and the error message was printed to stdout.

      Checked on master (4.3.0).

        Attachments

          Activity

            People

            Assignee:
            backlog-server-devtools DO NOT USE - Backlog - Dev Tools
            Reporter:
            oleg.pudeyev Oleg Pudeyev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: