[SERVER-31577] mongodb upgrade to 3.4 from 3.2,and configer server can not stepdown Created: 16/Oct/17  Updated: 07/Nov/17  Resolved: 16/Oct/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 3.4.9
Fix Version/s: None

Type: Question Priority: Critical - P2
Reporter: SuperSuJJ [X] Assignee: Mark Agarunov
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-31581 mongodb config server can not stepdown Closed
Participants:

 Description   

mongodb upgrade to 3.4 from 3.2,but after upgrade, configer server can not stepdown,and log is issue:
primary:
2017-10-16T10:45:18.963+0800 I ACCESS [conn1] SCRAM-SHA-1 authentication failed for admin on admin from client 192.168.169.61:62890 ; AuthenticationFailed: SCRAM-SHA-1 authentication failed, storedKey mismatch

secondary1:
2017-10-16T10:50:13.499+0800 I ACCESS [conn21] SCRAM-SHA-1 authentication failed for admin on admin from client 192.168.169.62:33442 ; AuthenticationFailed: SCRAM-SHA-1 authentication failed, storedKey mismatch

secondary2:
2017-10-16T10:45:10.686+0800 I ACCESS [conn17] SCRAM-SHA-1 authentication failed for admin on admin from client 192.168.169.62:46347 ; AuthenticationFailed: SCRAM-SHA-1 authentication failed, storedKey mismatch

the other sharding replica set are use the same keyfile,but they are normal use.



 Comments   
Comment by Mark Agarunov [ 16/Oct/17 ]

Hello Su

Thank you for the report. This ticket appears to be regarding the same behavior as SERVER-31581 so I've closed this as a duplicate.

Thanks,
Mark

Generated at Thu Feb 08 04:27:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.