-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: Btree
-
Storage Engines, Storage Engines - Transactions
-
None
-
None
{"t":{"$date":"2025-09-30T19:24:21.196+00:00"},"s":"F", "c":"CONTROL", "id":6384300, "ctx":"TimestampMonitor","msg":"Writing fatal message","attr":{"message":"Invalid access at address: 0x60\n"}}
{"t":{"$date":"2025-09-30T19:24:21.196+00:00"},"s":"F", "c":"CONTROL", "id":6384300, "ctx":"TimestampMonitor","msg":"Writing fatal message","attr":{"message":"Dumping siginfo (si_code=1): 0b 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n"}}
{"t":{"$date":"2025-09-30T19:24:21.196+00:00"},"s":"F", "c":"CONTROL", "id":6384300, "ctx":"TimestampMonitor","msg":"Writing fatal message","attr":{"message":"Got signal: 11 (Segmentation fault).\n"}}
logs with backtrace:
https://cloud-qa.mongodb.com/log/collection/request/68ae2ef5d5a5e71dfb786e9f/68dc2ed408b5f50078a69aca/download
cluster:
https://cloud-qa.mongodb.com/v2/68ae2ef5d5a5e71dfb786e9f#/clusters/detail/sls-smoke-qa-aws-use1
After the crash, the cluster restarted successfully, so this seems like just a race condition.
- related to
-
-
- Open
-