[SERVER-5114] Getting "profile: warning ns local.system.profile does not exist" errors after upgrade to mongodb 2.0.2 Created: 27/Feb/12  Updated: 17/Apr/17  Resolved: 16/Mar/17

Status: Closed
Project: Core Server
Component/s: Admin, Performance
Affects Version/s: 2.0.2
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Puneet Kandhari Assignee: Charlie Swanson
Resolution: Done Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Centos 5
Mongodb 2.0.2


Issue Links:
Depends
Duplicate
is duplicated by SERVER-5640 --profile option doesn't create the s... Closed
Related
Operating System: ALL
Participants:

 Description   

We just upgraded all our mongodb instances to 2.0.2

Mongodb runs as :

/usr/bin/mongod --journal -f /etc/mongod.conf --rest --syncdelay 20 --profile=1 --slowms=200

It doesn't seem to create the system.profile collection when the profile level is set to 1.

The temp fix is to up the profiling level to 2, and then set it back to 1.



 Comments   
Comment by Ian Whalen (Inactive) [ 07/Mar/17 ]

cnStoneFang can you provide exact steps to reproduce this on 3.2? From what we understand this problem doesn't exist anymore on master.

Comment by stone [X] [ 07/Dec/16 ]

why not have not been solved?
still met problem on mongo3.2.12

Comment by Puneet Kandhari [ 27/Feb/12 ]

Thanks scott,
the following steps fixed it

$: mongo
> use local
> db.setProfilingLevel(2);
> show collections
...
system.indexes
system.profile
> db.setProfilingLevel(1,200)

Comment by Scott Hernandez (Inactive) [ 27/Feb/12 ]

I've moved this to a server issue where it can be more directly addressed.

Generated at Thu Feb 08 03:07:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.