mongodump can't connect, how can I dump my mongodb dump without using mongodump
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
1
I have mongo 3.2.13 installed on OpenBSD 6.4. Mongo is installed via packages (pkg_add mongodb). The installation doesn't include mongodump, so I have to install it via the mongo-tools repo
mongodump can't detect any servers:
./bin/mongodump --verbose --port=27017 --host=127.0.0.1
2019-01-04T00:57:11.552-0800 Failed: error connecting to db server: no reachable servers
but mongod is running and I can connect:
mongo --verbose --port=27017 --host=127.0.0.1
MongoDB shell version: 3.2.13
connecting to: 127.0.0.1:27017/test
2019-01-04T01:02:58.148-0800 D NETWORK [thread1] creating new connection to:127.0.0.1:27017
2019-01-04T01:02:58.149-0800 D NETWORK [thread1] connected to server 127.0.0.1:27017 (127.0.0.1)
2019-01-04T01:02:58.149-0800 D NETWORK [thread1] connected connection!
I'm really only interested in one database which has about 25 collections. What series of commands could I use to back up this database (even if the commands have to be glued together with bash, node, ruby, etc)?
Edit: add mongo and mongdump version
mongo --version
MongoDB shell version: 3.2.13
./bin/mongodump --version
mongodump version: built-without-version-string
git version: built-without-git-spec
Go version: go1.11
os: openbsd
arch: amd64
compiler: gc
git log|head
commit 0c07b518aacdca382fc931a7946811cf16e46a78
Author: Ted Tuckman <ted.tuckman@mongodb.com>
Date: Thu Dec 20 16:19:20 2018 -0500
TOOLS-2109 Upgrade to go 1.11 in build script
commit 6dda8ce1473bfced00c4eff190918f29874d24bd
Author: Ted Tuckman <ted.tuckman@mongodb.com>
Date: Wed Dec 12 10:11:06 2018 -0500
Currently mongodump is built from origin/HEAD. I'll try checking out the 3.2 branch and rebuilding
mongodb database-backups mongodump openbsd
asked Jan 4 at 9:15
sheepdogsheepdog
467315
add a comment |
1
I have mongo 3.2.13 installed on OpenBSD 6.4. Mongo is installed via packages (pkg_add mongodb). The installation doesn't include mongodump, so I have to install it via the mongo-tools repo
mongodump can't detect any servers:
./bin/mongodump --verbose --port=27017 --host=127.0.0.1
2019-01-04T00:57:11.552-0800 Failed: error connecting to db server: no reachable servers
but mongod is running and I can connect:
mongo --verbose --port=27017 --host=127.0.0.1
MongoDB shell version: 3.2.13
connecting to: 127.0.0.1:27017/test
2019-01-04T01:02:58.148-0800 D NETWORK [thread1] creating new connection to:127.0.0.1:27017
2019-01-04T01:02:58.149-0800 D NETWORK [thread1] connected to server 127.0.0.1:27017 (127.0.0.1)
2019-01-04T01:02:58.149-0800 D NETWORK [thread1] connected connection!
I'm really only interested in one database which has about 25 collections. What series of commands could I use to back up this database (even if the commands have to be glued together with bash, node, ruby, etc)?
Edit: add mongo and mongdump version
mongo --version
MongoDB shell version: 3.2.13
./bin/mongodump --version
mongodump version: built-without-version-string
git version: built-without-git-spec
Go version: go1.11
os: openbsd
arch: amd64
compiler: gc
git log|head
commit 0c07b518aacdca382fc931a7946811cf16e46a78
Author: Ted Tuckman <ted.tuckman@mongodb.com>
Date: Thu Dec 20 16:19:20 2018 -0500
TOOLS-2109 Upgrade to go 1.11 in build script
commit 6dda8ce1473bfced00c4eff190918f29874d24bd
Author: Ted Tuckman <ted.tuckman@mongodb.com>
Date: Wed Dec 12 10:11:06 2018 -0500
Currently mongodump is built from origin/HEAD. I'll try checking out the 3.2 branch and rebuilding
mongodb database-backups mongodump openbsd
asked Jan 4 at 9:15
sheepdogsheepdog
467315
1
I have no clue what the problem might be, it doesnt make sense to me. Please additionally provide output ofmongo --versionandmongodump --version.
– DanFromGermany
Jan 4 at 9:28
@DanFromGermany updated to add version info
– sheepdog
Jan 4 at 9:41
1
@DanFromGermany Thanks for your comments. It lead me in the right direction. I checked out the 3.2 branch of mongo-tools, rebuilt mongodump, and everything worked!
– sheepdog
Jan 4 at 9:48
Nice! Only an API / version mismatch like this can cause such strange behaviour :D Glad to hear you got it working!
– DanFromGermany
Jan 4 at 10:16
add a comment |
1
1
1
I have mongo 3.2.13 installed on OpenBSD 6.4. Mongo is installed via packages (pkg_add mongodb). The installation doesn't include mongodump, so I have to install it via the mongo-tools repo
mongodump can't detect any servers:
./bin/mongodump --verbose --port=27017 --host=127.0.0.1
2019-01-04T00:57:11.552-0800 Failed: error connecting to db server: no reachable servers
but mongod is running and I can connect:
mongo --verbose --port=27017 --host=127.0.0.1
MongoDB shell version: 3.2.13
connecting to: 127.0.0.1:27017/test
2019-01-04T01:02:58.148-0800 D NETWORK [thread1] creating new connection to:127.0.0.1:27017
2019-01-04T01:02:58.149-0800 D NETWORK [thread1] connected to server 127.0.0.1:27017 (127.0.0.1)
2019-01-04T01:02:58.149-0800 D NETWORK [thread1] connected connection!
I'm really only interested in one database which has about 25 collections. What series of commands could I use to back up this database (even if the commands have to be glued together with bash, node, ruby, etc)?
Edit: add mongo and mongdump version
mongo --version
MongoDB shell version: 3.2.13
./bin/mongodump --version
mongodump version: built-without-version-string
git version: built-without-git-spec
Go version: go1.11
os: openbsd
arch: amd64
compiler: gc
git log|head
commit 0c07b518aacdca382fc931a7946811cf16e46a78
Author: Ted Tuckman <ted.tuckman@mongodb.com>
Date: Thu Dec 20 16:19:20 2018 -0500
TOOLS-2109 Upgrade to go 1.11 in build script
commit 6dda8ce1473bfced00c4eff190918f29874d24bd
Author: Ted Tuckman <ted.tuckman@mongodb.com>
Date: Wed Dec 12 10:11:06 2018 -0500
Currently mongodump is built from origin/HEAD. I'll try checking out the 3.2 branch and rebuilding
mongodb database-backups mongodump openbsd
asked Jan 4 at 9:15
sheepdogsheepdog
467315
I have mongo 3.2.13 installed on OpenBSD 6.4. Mongo is installed via packages (pkg_add mongodb). The installation doesn't include mongodump, so I have to install it via the mongo-tools repo
mongodump can't detect any servers:
./bin/mongodump --verbose --port=27017 --host=127.0.0.1
2019-01-04T00:57:11.552-0800 Failed: error connecting to db server: no reachable servers
but mongod is running and I can connect:
mongo --verbose --port=27017 --host=127.0.0.1
MongoDB shell version: 3.2.13
connecting to: 127.0.0.1:27017/test
2019-01-04T01:02:58.148-0800 D NETWORK [thread1] creating new connection to:127.0.0.1:27017
2019-01-04T01:02:58.149-0800 D NETWORK [thread1] connected to server 127.0.0.1:27017 (127.0.0.1)
2019-01-04T01:02:58.149-0800 D NETWORK [thread1] connected connection!
I'm really only interested in one database which has about 25 collections. What series of commands could I use to back up this database (even if the commands have to be glued together with bash, node, ruby, etc)?
Edit: add mongo and mongdump version
mongo --version
MongoDB shell version: 3.2.13
./bin/mongodump --version
mongodump version: built-without-version-string
git version: built-without-git-spec
Go version: go1.11
os: openbsd
arch: amd64
compiler: gc
git log|head
commit 0c07b518aacdca382fc931a7946811cf16e46a78
Author: Ted Tuckman <ted.tuckman@mongodb.com>
Date: Thu Dec 20 16:19:20 2018 -0500
TOOLS-2109 Upgrade to go 1.11 in build script
commit 6dda8ce1473bfced00c4eff190918f29874d24bd
Author: Ted Tuckman <ted.tuckman@mongodb.com>
Date: Wed Dec 12 10:11:06 2018 -0500
Currently mongodump is built from origin/HEAD. I'll try checking out the 3.2 branch and rebuilding
mongodb database-backups mongodump openbsd
mongodb database-backups mongodump openbsd
asked Jan 4 at 9:15
sheepdogsheepdog
467315
asked Jan 4 at 9:15
sheepdogsheepdog
467315
edited Jan 4 at 9:40
sheepdog
asked Jan 4 at 9:15
sheepdogsheepdog
467315
asked Jan 4 at 9:15
sheepdogsheepdog
467315
asked Jan 4 at 9:15
sheepdogsheepdog
467315
467315
1
I have no clue what the problem might be, it doesnt make sense to me. Please additionally provide output ofmongo --versionandmongodump --version.
– DanFromGermany
Jan 4 at 9:28
@DanFromGermany updated to add version info
– sheepdog
Jan 4 at 9:41
1
@DanFromGermany Thanks for your comments. It lead me in the right direction. I checked out the 3.2 branch of mongo-tools, rebuilt mongodump, and everything worked!
– sheepdog
Jan 4 at 9:48
Nice! Only an API / version mismatch like this can cause such strange behaviour :D Glad to hear you got it working!
– DanFromGermany
Jan 4 at 10:16
add a comment |
1
I have no clue what the problem might be, it doesnt make sense to me. Please additionally provide output ofmongo --versionandmongodump --version.
– DanFromGermany
Jan 4 at 9:28
@DanFromGermany updated to add version info
– sheepdog
Jan 4 at 9:41
1
@DanFromGermany Thanks for your comments. It lead me in the right direction. I checked out the 3.2 branch of mongo-tools, rebuilt mongodump, and everything worked!
– sheepdog
Jan 4 at 9:48
Nice! Only an API / version mismatch like this can cause such strange behaviour :D Glad to hear you got it working!
– DanFromGermany
Jan 4 at 10:16
1
1
I have no clue what the problem might be, it doesnt make sense to me. Please additionally provide output of
mongo --version and mongodump --version.– DanFromGermany
Jan 4 at 9:28
I have no clue what the problem might be, it doesnt make sense to me. Please additionally provide output of
mongo --version and mongodump --version.– DanFromGermany
Jan 4 at 9:28
@DanFromGermany updated to add version info
– sheepdog
Jan 4 at 9:41
@DanFromGermany updated to add version info
– sheepdog
Jan 4 at 9:41
1
1
@DanFromGermany Thanks for your comments. It lead me in the right direction. I checked out the 3.2 branch of mongo-tools, rebuilt mongodump, and everything worked!
– sheepdog
Jan 4 at 9:48
@DanFromGermany Thanks for your comments. It lead me in the right direction. I checked out the 3.2 branch of mongo-tools, rebuilt mongodump, and everything worked!
– sheepdog
Jan 4 at 9:48
Nice! Only an API / version mismatch like this can cause such strange behaviour :D Glad to hear you got it working!
– DanFromGermany
Jan 4 at 10:16
Nice! Only an API / version mismatch like this can cause such strange behaviour :D Glad to hear you got it working!
– DanFromGermany
Jan 4 at 10:16
add a comment |
1 Answer
1
active
oldest
votes
1
Make sure you have compiled a compatible version of mongodump, see
mongodump --version
mongo --version
answered Jan 4 at 10:15
DanFromGermanyDanFromGermany
20.1k74796
add a comment |
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%2f54035972%2fmongodump-cant-connect-how-can-i-dump-my-mongodb-dump-without-using-mongodump%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
Make sure you have compiled a compatible version of mongodump, see
mongodump --version
mongo --version
answered Jan 4 at 10:15
DanFromGermanyDanFromGermany
20.1k74796
add a comment |
1
Make sure you have compiled a compatible version of mongodump, see
mongodump --version
mongo --version
answered Jan 4 at 10:15
DanFromGermanyDanFromGermany
20.1k74796
add a comment |
1
1
1
Make sure you have compiled a compatible version of mongodump, see
mongodump --version
mongo --version
answered Jan 4 at 10:15
DanFromGermanyDanFromGermany
20.1k74796
Make sure you have compiled a compatible version of mongodump, see
mongodump --version
mongo --version
answered Jan 4 at 10:15
DanFromGermanyDanFromGermany
20.1k74796
answered Jan 4 at 10:15
DanFromGermanyDanFromGermany
20.1k74796
answered Jan 4 at 10:15
DanFromGermanyDanFromGermany
20.1k74796
answered Jan 4 at 10:15
DanFromGermanyDanFromGermany
20.1k74796
20.1k74796
add a comment |
add a comment |
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%2f54035972%2fmongodump-cant-connect-how-can-i-dump-my-mongodb-dump-without-using-mongodump%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
1
I have no clue what the problem might be, it doesnt make sense to me. Please additionally provide output of
mongo --versionandmongodump --version.– DanFromGermany
Jan 4 at 9:28
@DanFromGermany updated to add version info
– sheepdog
Jan 4 at 9:41
1
@DanFromGermany Thanks for your comments. It lead me in the right direction. I checked out the 3.2 branch of mongo-tools, rebuilt mongodump, and everything worked!
– sheepdog
Jan 4 at 9:48
Nice! Only an API / version mismatch like this can cause such strange behaviour :D Glad to hear you got it working!
– DanFromGermany
Jan 4 at 10:16