-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 6.0.4
-
Component/s: None
-
None
-
Service Arch
-
ALL
-
-
Service Arch 2023-03-20, Service Arch 2023-04-03, Service Arch 2023-04-17, Service Arch 2023-05-15, Service Arch 2023-05-29
We are running 6.0.4 on Ubuntu 22.04 jammy. We got an alert earlier from our app saying it lost connection to a local mongos router. Mongos.log shows the following:
{"t":\{"$date":"2023-03-09T08:21:58.772-05:00"},"s":"F", "c":"CONTROL", "id":6384300, "ctx":"conn121","msg":"Writing fatal message","attr":{"message":"Invalid access at address: 0\n"}}
{"t":\{"$date":"2023-03-09T08:21:58.772-05:00"},"s":"F", "c":"CONTROL", "id":6384300, "ctx":"conn121","msg":"Writing fatal message","attr":{"message":"Got signal: 11 (Segmentation fault).\n"}}
{"t":\{"$date":"2023-03-09T08:21:58.772-05:00"},"s":"F", "c":"ASSERT", "id":23079, "ctx":"conn127","msg":"Invariant failure","attr":{"expr":"!callback","file":"src/mongo/util/future_impl.h","line":443}}
{"t":\{"$date":"2023-03-09T08:21:58.772-05:00"},"s":"F", "c":"ASSERT", "id":23080, "ctx":"conn127","msg":"\n\n***aborting after invariant() failure\n\n"}
This is the first time I've ever seen this error.
I have saved the mongos.log and diagnostic data and can upload it for analysis.