Mongod - Can't access database after repair











up vote
1
down vote

favorite












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.










share|improve this question






















  • 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 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 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 at 2:51















up vote
1
down vote

favorite












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.










share|improve this question






















  • 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 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 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 at 2:51













up vote
1
down vote

favorite









up vote
1
down vote

favorite











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.










share|improve this question













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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 19 at 12:51









olegario

147220




147220












  • 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 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 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 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 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 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 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 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 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 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 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 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 at 2:51

















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',
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


















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






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














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





















































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







Popular posts from this blog

404 Error Contact Form 7 ajax form submitting

How to know if a Active Directory user can login interactively

Refactoring coordinates for Minecraft Pi buildings written in Python