Mongod - Can't access database after repair
1
I was suffering with some issues with my database, that is using Mongd. So, I decided to run the following command:
sudo mongod --repair --dbpath /var/lib/mongodb
The problem is, after that the service stoped to boot when I start my instance and also every time I try to acess the database, mongo says:
35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.347+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.349+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.350+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.488+0000 I ACCESS [conn6] SCRAM-SHA-1 authentication failed for user on admin from client 52.33.160.17 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.490+0000 I ACCESS [conn6] SCRAM-SHA-1 authentication failed for user on admin from client 52.33.160.17 ; UserNotFound: Could not find user user@admin
Why this is happening? What can I do? I lost my DB?
The database was running in version 3.2 in a EC2 instance.
mongodb maintenance repair
asked Nov 19 '18 at 12:51
olegarioolegario
165220
add a comment |
1
I was suffering with some issues with my database, that is using Mongd. So, I decided to run the following command:
sudo mongod --repair --dbpath /var/lib/mongodb
The problem is, after that the service stoped to boot when I start my instance and also every time I try to acess the database, mongo says:
35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.347+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.349+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.350+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.488+0000 I ACCESS [conn6] SCRAM-SHA-1 authentication failed for user on admin from client 52.33.160.17 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.490+0000 I ACCESS [conn6] SCRAM-SHA-1 authentication failed for user on admin from client 52.33.160.17 ; UserNotFound: Could not find user user@admin
Why this is happening? What can I do? I lost my DB?
The database was running in version 3.2 in a EC2 instance.
mongodb maintenance repair
asked Nov 19 '18 at 12:51
olegarioolegario
165220
this looks like some kind of authentication issue. Did you enable authorization in the past? Have you created a user called "user" on admin database? Please login to mongodb as super admin user and check if a user called "user" exists in the db.
– Sandeep
Nov 19 '18 at 13:12
@Sandeep Yes, the authentication is enabled. The problem is, every time I try to execute the commandmongodit show that message above.
– olegario
Nov 19 '18 at 13:56
@olegario it is showing two IP addresses35.162.76.212and52.33.160.17trying to authenticate but failing. Are you familiar with those addresses? Note that this has nothing to do with--repair. What problem are you trying to solve here?
– Kevin Adistambha
Nov 20 '18 at 2:51
add a comment |
1
1
1
I was suffering with some issues with my database, that is using Mongd. So, I decided to run the following command:
sudo mongod --repair --dbpath /var/lib/mongodb
The problem is, after that the service stoped to boot when I start my instance and also every time I try to acess the database, mongo says:
35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.347+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.349+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.350+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.488+0000 I ACCESS [conn6] SCRAM-SHA-1 authentication failed for user on admin from client 52.33.160.17 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.490+0000 I ACCESS [conn6] SCRAM-SHA-1 authentication failed for user on admin from client 52.33.160.17 ; UserNotFound: Could not find user user@admin
Why this is happening? What can I do? I lost my DB?
The database was running in version 3.2 in a EC2 instance.
mongodb maintenance repair
asked Nov 19 '18 at 12:51
olegarioolegario
165220
I was suffering with some issues with my database, that is using Mongd. So, I decided to run the following command:
sudo mongod --repair --dbpath /var/lib/mongodb
The problem is, after that the service stoped to boot when I start my instance and also every time I try to acess the database, mongo says:
35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.347+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.349+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.350+0000 I ACCESS [conn2] SCRAM-SHA-1 authentication failed for user on admin from client 35.162.76.212 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.488+0000 I ACCESS [conn6] SCRAM-SHA-1 authentication failed for user on admin from client 52.33.160.17 ; UserNotFound: Could not find user user@admin
2018-11-19T12:46:08.490+0000 I ACCESS [conn6] SCRAM-SHA-1 authentication failed for user on admin from client 52.33.160.17 ; UserNotFound: Could not find user user@admin
Why this is happening? What can I do? I lost my DB?
The database was running in version 3.2 in a EC2 instance.
mongodb maintenance repair
mongodb maintenance repair
asked Nov 19 '18 at 12:51
olegarioolegario
165220
asked Nov 19 '18 at 12:51
olegarioolegario
165220
asked Nov 19 '18 at 12:51
olegarioolegario
165220
asked Nov 19 '18 at 12:51
olegarioolegario
165220
asked Nov 19 '18 at 12:51
olegarioolegario
165220
165220
this looks like some kind of authentication issue. Did you enable authorization in the past? Have you created a user called "user" on admin database? Please login to mongodb as super admin user and check if a user called "user" exists in the db.
– Sandeep
Nov 19 '18 at 13:12
@Sandeep Yes, the authentication is enabled. The problem is, every time I try to execute the commandmongodit show that message above.
– olegario
Nov 19 '18 at 13:56
@olegario it is showing two IP addresses35.162.76.212and52.33.160.17trying to authenticate but failing. Are you familiar with those addresses? Note that this has nothing to do with--repair. What problem are you trying to solve here?
– Kevin Adistambha
Nov 20 '18 at 2:51
add a comment |
this looks like some kind of authentication issue. Did you enable authorization in the past? Have you created a user called "user" on admin database? Please login to mongodb as super admin user and check if a user called "user" exists in the db.
– Sandeep
Nov 19 '18 at 13:12
@Sandeep Yes, the authentication is enabled. The problem is, every time I try to execute the commandmongodit show that message above.
– olegario
Nov 19 '18 at 13:56
@olegario it is showing two IP addresses35.162.76.212and52.33.160.17trying to authenticate but failing. Are you familiar with those addresses? Note that this has nothing to do with--repair. What problem are you trying to solve here?
– Kevin Adistambha
Nov 20 '18 at 2:51
this looks like some kind of authentication issue. Did you enable authorization in the past? Have you created a user called "user" on admin database? Please login to mongodb as super admin user and check if a user called "user" exists in the db.
– Sandeep
Nov 19 '18 at 13:12
this looks like some kind of authentication issue. Did you enable authorization in the past? Have you created a user called "user" on admin database? Please login to mongodb as super admin user and check if a user called "user" exists in the db.
– Sandeep
Nov 19 '18 at 13:12
@Sandeep Yes, the authentication is enabled. The problem is, every time I try to execute the command
mongod it show that message above.– olegario
Nov 19 '18 at 13:56
@Sandeep Yes, the authentication is enabled. The problem is, every time I try to execute the command
mongod it show that message above.– olegario
Nov 19 '18 at 13:56
@olegario it is showing two IP addresses
35.162.76.212 and 52.33.160.17 trying to authenticate but failing. Are you familiar with those addresses? Note that this has nothing to do with --repair. What problem are you trying to solve here?– Kevin Adistambha
Nov 20 '18 at 2:51
@olegario it is showing two IP addresses
35.162.76.212 and 52.33.160.17 trying to authenticate but failing. Are you familiar with those addresses? Note that this has nothing to do with --repair. What problem are you trying to solve here?– Kevin Adistambha
Nov 20 '18 at 2:51
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53375056%2fmongod-cant-access-database-after-repair%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53375056%2fmongod-cant-access-database-after-repair%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
this looks like some kind of authentication issue. Did you enable authorization in the past? Have you created a user called "user" on admin database? Please login to mongodb as super admin user and check if a user called "user" exists in the db.
– Sandeep
Nov 19 '18 at 13:12
@Sandeep Yes, the authentication is enabled. The problem is, every time I try to execute the command
mongodit show that message above.– olegario
Nov 19 '18 at 13:56
@olegario it is showing two IP addresses
35.162.76.212and52.33.160.17trying to authenticate but failing. Are you familiar with those addresses? Note that this has nothing to do with--repair. What problem are you trying to solve here?– Kevin Adistambha
Nov 20 '18 at 2:51