[SERVER-27669] Not all errors are logged Created: 12/Jan/17 Updated: 30/Jan/17 Resolved: 30/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 3.2.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | bgentry | Assignee: | Kelsey Schubert |
| 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 |
|
We receive emails when a user encounters an error. When it is a mongo error, we expect to be able to open the log file and find the command the user was attempting when the error occurred. For example: MongoDB.Driver.MongoCommandException: Command find failed: errmsg: "Sort operation used more than the maximum 268435456 bytes of RAM. Add an index, or specify a smaller limit.". These errors are not always in the mongo log file |
| Comments |
| Comment by Kelsey Schubert [ 30/Jan/17 ] |
|
Hi bgentry, Thank you for the report. This improvement request appears to be a duplicate of Kind regards, |