[SERVER-59755] Exception during log, message not written to stream, crashes server Created: 02/Sep/21 Updated: 13/Sep/21 Resolved: 13/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dave S | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Windows Server 2019. Replicaset with three members, no sharding. Feature compatibility still set to 4.2. |
||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
I've had two crashes recently since upgrading from MongoDB 4.2 to 4.4.8, both with the same error messages. One crash on a primary the other on a secondary. See attached log. |
| Comments |
| Comment by Kelsey Schubert [ 13/Sep/21 ] |
|
Hi radardave, The error message: "Unable to access windows registry" suggests an issue beneath MongoDB. The failing command is here: https://docs.microsoft.com/en-us/cpp/atl/reference/cregkey-class?view=msvc-160#open. I would recommend investigating system issues and resource contention on the underlying host. As this issue does not appear to be a bug in MongoDB, I would encourage you to ask our community by posting on the MongoDB Developer Community Forums. Thanks, |
| Comment by Dave S [ 08/Sep/21 ] |
|
My best guess for the source of the error is the first error message logged, "Can't get KeepAlive parameter". The only source code with this message is in https://github.com/mongodb/mongo/blob/master/src/mongo/util/net/socket_utils.cpp line 122. "Can't get KeepAlive parameter" was present in all crash logs just before the crash occurred. This message was not present elsewhere in the recent logs. |
| Comment by Dave S [ 08/Sep/21 ] |
|
Primary crashed with the same error. This puts us at three crashes total, each 7 days apart. |