-
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).
- duplicates
-
SERVER-5114 Getting "profile: warning ns local.system.profile does not exist" errors after upgrade to mongodb 2.0.2
-
- Closed
-