Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Unable to add secondary node

Description

Hi Team,

We have a 3-node MongoDB replica setup running Percona Mongo 7.0.15. As part of the Ubuntu kernel upgrade, we rebooted one of the nodes. However, after the reboot, it is unable to catch up with the primary and is throwing the following error:

[Include error message here]

Please advise on the next steps to resolve this issue.

 

{"t":{"$date":" ,"s":"I", "c":"ACCESS", "id":5286307, "ctx":"conn9343","msg":"Failed to authenticate","attr":{"client":"xxx","isSpeculative":false,"isClusterMember":true,"mechanism":"SCRAM-SHA-256","user":"__system","db":"local","error":"AuthenticationFailed: SCRAM authentication failed, storedKey mismatch","result":18,"metrics":{"conversation_duration":{"micros":1501,"summary":{"0":{"step":1,"step_total":2,"duration_micros":43},"1":{"step":2,"step_total":2,"duration_micros":9}}}},"extraInfo":{}}}

Environment

None

Activity

radoslaw.szulgo March 11, 2025 at 1:34 PM

Thanks , we’re unable to tell the root cause as provided logs don’t reveal much. I’m happy the issue is gone. In case you need some further assistance - let us know.

bhavik mistry February 25, 2025 at 6:21 AM

Issue got resolved after promote another node as primary..But still not sure about root cause disappointed face

Cannot Reproduce

Details

Security Level Help

None

Assignee

Reporter

Labels

Needs QA

Yes

Start date

Components

Sprint

Affects versions

Priority

Smart Checklist

Created February 19, 2025 at 3:48 AM
Updated March 11, 2025 at 1:34 PM
Resolved March 11, 2025 at 1:34 PM

Flag notifications