[SERVER-42571] Collect Windows event logs on remote machine during powercycle Created: 01/Aug/19 Updated: 29/Oct/23 Resolved: 01/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.1, 4.3.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tig-evgconfig, tig-powercycle | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||
| Sprint: | STM 2019-08-12 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 26 | ||||||||||||
| Story Points: | 2 | ||||||||||||
| Description |
|
We've had many failures since upgrading to Windows Server 2016 where the mongod service fails to start or the process abruptly terminates after having started. The Windows event logs revealed that after notmyfault.exe is used to crash the virtual machine, the log and data files, or in some cases the mongod.exe executable itself, cannot be opened. We should collect the recent messages from the Application, Security, and System event logs on Windows using the wevtutil utility in order to have more diagnostics around this issue and for other mysterious ones that will surely come up in the future. |
| Comments |
| Comment by Githook User [ 13/Aug/19 ] |
|
Author: {'name': 'Max Hirschhorn', 'username': 'visemet', 'email': 'max.hirschhorn@mongodb.com'}Message: (cherry picked from commit b59d4a9c69407295619870f810e13215e01efb12) |
| Comment by Githook User [ 01/Aug/19 ] |
|
Author: {'name': 'Max Hirschhorn', 'username': 'visemet', 'email': 'max.hirschhorn@mongodb.com'}Message: |