[SERVER-5640] --profile option doesn't create the system.profile collection if it doesn't already exist Created: 17/Apr/12 Updated: 20/Sep/12 Resolved: 17/May/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Performance |
| Affects Version/s: | 2.0.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
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). |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 18/Apr/12 ] |
|
may actually be a dup of |