--profile option doesn't create the system.profile collection if it doesn't already exist

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 2.0.4
    • Component/s: Admin, Performance
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      If you start mongod with --profile to enable profiling, nothing will actually be recorded because the system.profile collection doesn't exist. You can then either manually create system.profile with the createCollection command, or you can setProfilingLevel to 0 then back to the level you want (which will create system.profile for you).

            Assignee:
            Unassigned
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: