[SERVER-29975] Better reporting of configuration errors Created: 05/Jul/17  Updated: 27/Oct/23  Resolved: 12/Jul/17

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Lorne Schachter Assignee: Unassigned
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-29964 Better recognition of invalid options Closed
Operating System: ALL
Participants:

 Description   

If auditing is being enabled in OpsManager and being sent to a file, one of the required arguments is 'auditLogPath' which needs to be a pathname to a file that will be the audit log. If the value is incorrect, mongod should return an error to stderr so that OpsManager can recognize the failure and report it to the user instead of leaving the configuration in an inconsistent state.



 Comments   
Comment by Eric Milkie [ 05/Jul/17 ]

Also, I think mongod already puts an error in the system log (and returns errorcode 1) if the audit log file cannot be opened:
2017-07-05T11:26:42.869-0400 F CONTROL [main] Failed global initialization: FileNotOpen: Failed to open "/asdf"

Comment by Eric Milkie [ 05/Jul/17 ]

Do you mean "auditPath"? I don't see "auditLogPath" as a possible argument.

Generated at Thu Feb 08 04:22:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.