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

setParameter for "logLevel" logged incorrectly

    XMLWordPrintable

    Details

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

      Description

      Looking at the mongod log after issuing a setParameter command setting logLevel to 2, the log reports that I did something different:
      Shell:

      > db.adminCommand({ setParameter : 1, logLevel : 2 })
      { "was" : 0, "ok" : 1 }
      >

      mongod log:

      Mon May 21 19:46:27 [conn1] runQuery called admin.$cmd { replSetGetStatus: 1.0, forShell: 1.0 }
      Mon May 21 19:46:27 [conn1] run command admin.$cmd { replSetGetStatus: 1.0, forShell: 1.0 }
      Mon May 21 19:46:27 [conn1] command: { replSetGetStatus: 1.0, forShell: 1.0 }
      Mon May 21 19:46:27 [conn1] command admin.$cmd command: { replSetGetStatus: 1.0, forShell: 1.0 } ntoreturn:1 keyUpdates:0 reslen:76 0ms

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tad Tad Marshall
              Reporter:
              tad Tad Marshall
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: