mongodb upgrade to 3.4 from 3.2,and configer server can not stepdown

XMLWordPrintableJSON

    • Type: Question
    • Resolution: Duplicate
    • Priority: Critical - P2
    • None
    • Affects Version/s: 3.4.9
    • Component/s: None
    • None
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Mark Agarunov (Inactive)
            Reporter:
            SuperSuJJ [X]
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: