We are running a self-hosted mongodb deployment as a three member replica set (PSA), recently upgraded from mongodb 6.0.3. We are running in a containerized environment. Every so often, I see logs like the following:
{"t":{"$date":"2025-02-10T17:08:53.642+00:00"},"s":"I", "c":"ACCESS", "id":5286307, "ctx":"conn440","msg":"Failed to authenticate","attr":{"client":"172.22.0.1:39686","isSpeculative":false,"isClusterMember":false,"mechanism":"","user":"","db":"","error":"AuthenticationAbandoned: Authentication session abandoned, client has likely disconnected","result":337,"metrics":{"conversation_duration":{"micros":358000215,"summary":{}}},"extraInfo":{}}}
I see no evidence of failure to replicate or other problems. The message may be logged by any of the 3 members of the replica set. The log message does not show up if we deploy our application without a replica set. What does this log mean? Is there a way to address a problem it relates to, or is it “expected”?
sho_okada
(Sho Okada)
2
I experienced the same issue.
I upgraded from 6.0.15 to 7.0.16 to 8.0.4, and the issue occurred on 7.0.16 and 8.0.4.
It is occurring on mongo running on 3 replica sets.
It is also happening on a mongo with 5 × 2 shard servers.
Replication is not affected and nothing else is happening except this error.
Does anyone know what this log means?
Can mongo work properly in the future with this error?
What should we do if we need to do something to mongo (e.g. upgrade to the latest version)?
If anyone knows, please comment.
After getting no response here, I created a JIRA ticket. See https://jira.mongodb.org/browse/SERVER-100979.
1 Like