[SERVER-30230] Detailed error message when mongod fails to start to because systemLog.path points to a directory Created: 19/Jul/17 Updated: 30/Oct/23 Resolved: 07/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.12 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andrey Brindeyev | Assignee: | Spencer Jackson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platforms 2017-08-21 |
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
When mongod have directory instead of file in the systemLog.path configuration option, the error message on RHEL-style Linux distros isn't explicit about the failure and the directory itself is empty. This confuses the customer:
|
| Comments |
| Comment by Githook User [ 07/Aug/17 ] |
|
Author: {'username': 'spencerjackson', 'email': 'spencer.jackson@mongodb.com', 'name': 'Spencer Jackson'}Message: |
| Comment by Spencer Jackson [ 01/Aug/17 ] |
|
I'm thinking of appending a line to this output, to the effect of:
|