[SERVER-44171] Improved logging for disk space issues Created: 23/Oct/19 Updated: 29/Oct/23 Resolved: 20/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Barry McConville | Assignee: | Sara Golemon |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Minor Change |
| Sprint: | Security 2019-12-16, Security 2019-12-30 |
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
Hi Guys,
If the AuditLog is on a separate mount point and runs out of disk space the mongod will crash and be stuck in a restart loop. The backtrace within the mongod logs do not contain any meaningful entries to indicate the root cause, other than it was working on an auditing event. It would be useful if we printed no space left on device /path Thanks Barry |
| Comments |
| Comment by Githook User [ 20/Dec/19 ] |
|
Author: {'name': 'Sara Golemon', 'email': 'sara.golemon@mongodb.com', 'username': 'sgolemon'}Message: |