[SERVER-13746] mongod doesn't shut down when it can't write to log file with auditing enabled Created: 25/Apr/14 Updated: 10/Dec/14 Resolved: 16/Jul/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 2.6.1-rc0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Michael Grundy | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Running 2.6.1-rc0 on CentOS 6, dbpath is on a separate drive. Used
mongod started with auditDestination syslog:
When drive fills up and mongod can't write the log anymore, nothing happens. With auditing on it should shut down and write an audit message if possible. |
| Comments |
| Comment by Eric Milkie [ 25/Apr/14 ] |
|
I'm not sure we need to do this. Perhaps we could make a shutdownOnLogFailure server parameter to allow users to elect to have the server shut down when it runs out of log space, but it shouldn't be linked to whether auditing is turned on. |