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

Bypass auth check when logging "ClientCursor::yield can't unlock" message

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • 2.3.2
    • 2.0.2
    • Logging, Security
    • None

    Description

      When auth is enabled, certain log operations aren't as informative as they might be. For example, the warning about not yielding because the recursive lock is held tries to get the current op's info, which is only available to threads authenticated to the admin db, so the warning message reports 'top:

      { err : "unauthorized" }

      '.

      So maybe log messages should make a practice of bypassing auth checks of this sort, so long as we're only sending log output to files and other things that only ops folks can get at.

      Attachments

        Activity

          People

            spencer@mongodb.com Spencer Brody (Inactive)
            richard.kreuter Richard Kreuter (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: