[SERVER-38281] TLS info message isn't captured into system log Created: 27/Nov/18 Updated: 29/Oct/23 Resolved: 05/Dec/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.5, 4.1.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Sara Golemon |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Minor Change | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v4.0
|
||||
| Sprint: | Security 2018-12-17 | ||||
| Participants: | |||||
| Description |
|
Because we are logging a TLS message in the command line processing code itself, the logging occurs prior to the parsing of the --logpath parameter. This means any log messages go to stdout instead of the log file. This is apparent if you start mongod with --logpath:
(and then no other terminal messages appear) |
| Comments |
| Comment by Githook User [ 08/Dec/18 ] |
|
Author: {'name': 'Sara Golemon', 'email': 'sara.golemon@mongodb.com', 'username': 'sgolemon'}Message: (cherry picked from commit dfa007f46708ade8f66ae64bbcb9fd5744f96602) |
| Comment by Githook User [ 06/Dec/18 ] |
|
Author: {'name': 'Sara Golemon', 'email': 'sara.golemon@mongodb.com', 'username': 'sgolemon'}Message: |
| Comment by Githook User [ 05/Dec/18 ] |
|
Author: {'name': 'Sara Golemon', 'email': 'sara.golemon@mongodb.com', 'username': 'sgolemon'}Message: Revert " This reverts commit e0932edfcb5704629421b5cf6cfc5457c70f0d6e. |
| Comment by Githook User [ 05/Dec/18 ] |
|
Author: {'name': 'Sara Golemon', 'email': 'sara.golemon@mongodb.com', 'username': 'sgolemon'}Message: |