Command 'fsync' failed: exception: fsync: profiling must be off to enter locked mode (response:

{ "errmsg" : "exception: fsync: profiling must be off to enter locked mode", "code" : 12033, "ok" : 0.0 }

)

I can not find this anywhere in documentation. It is an issue that I faced tonight, and this belongs either in the db.fsyncLock() or db.setProfilingLevel() documentation. Or both.

Had I know ahead of time that you could not fsyncLock a server when profiling was enabled, I would have never enabled it.