Help you a great god, and had a 3.2 replic set, now upgraded to 4.0 or 4.2, use mongorestore recover data error, to restore the admin report Failed: restore error: error running the merge command: Missing expected field "db", see the log found SASL authentication problem SCRAM - SHA - 1 authentication Failed for XXX on the admin from client 111.200.241.218:48071; UnsupportedFormat: User documents must dojo.provide credentials for and/or SCRAM SCRAM - SHA - 1 - SHA - 256, database is a great god, please have the same problem, how to solve

CodePudding user response:

1 the authentication failed for XXX on the admin from client 111.200.241.218:48071
-- -- -- -- -- -- -- -- -- -- - this is a connection failure? You directly use mongo client connection is what circumstance?

CodePudding user response:

reference no. 1 floor ZJCXC -- personal WeChat public same response:

1 authentication failed for XXX on the admin from client 111.200.241.218:48071
-- -- -- -- -- -- -- -- -- -- - this is a connection failure? You directly use mongo client connection is what circumstance?

This is authentication error, the new mongo use and/or SCRAM SCRAM - SHA - 1 - SHA - 256 certification, but also in the use of directing a 3.6 - CR mode, so when data recovery is in the error, the above is my understanding, do not know right, also don't know how to deal with

CodePudding user response:

Check the website, only support upgrade to 4.0 3.6, to upgrade from 4.0 to 4.2
3.2 are you from in the past, there was a problem with compatibility should be
If mongo connection is no problem, then try resotre, does not contain the admin repository

CodePudding user response:

reference no. 3 floor ZJCXC - personal WeChat public same response:

checked the website, only support upgrade to 4.0 3.6, then the upgrade from 4.0 to 4.2
3.2 are you from in the past, there was a problem with compatibility should be
If mongo connection is no problem, then try resotre, does not contain the admin repository

Ali's recent plan to use mongo shake do migration, the 4.0 uninstalled, with 4.2, but doing rs. Initiate an error (} {XXX), true suit, also no problem before
{
"Ok" : 0,
"Errmsg" : "No host described in the new configuration for 1 up set rs maps to this node",
"Code" : 93,
"CodeName" : "InvalidReplicaSetConfig
"}

CodePudding user response:

Mongo while in getting better and better, which leads to the version update too fast, worse compatibility, upgrade will lead to all sorts of problems