[DOCS-252] Document fsyncLock() requiring profiling be turned off Created: 23/Jun/12 Updated: 08/Sep/12 Resolved: 24/Jul/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ryan Hoffman | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 11 years, 30 weeks, 1 day ago |
| Description |
|
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. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 24/Jul/12 ] |
|
epc |
| Comment by auto [ 24/Jul/12 ] |
|
Author: {u'date': u'2012-07-23T12:34:08-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: merge: adding a note for |
| Comment by auto [ 24/Jul/12 ] |
|
Author: {u'date': u'2012-07-23T11:51:01-07:00', u'email': u'epc@acm.org', u'name': u'Ed Costello'}Message: Create and include note addressing |
| Comment by auto [ 23/Jul/12 ] |
|
Author: {u'date': u'2012-07-23T12:34:08-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: merge: adding a note for |
| Comment by auto [ 23/Jul/12 ] |
|
Author: {u'date': u'2012-07-23T11:51:01-07:00', u'email': u'epc@acm.org', u'name': u'Ed Costello'}Message: Create and include note addressing |