mongorestore

mongorestore random crash (fatal error)

时间秒杀一切 提交于 2019-12-07 00:57:23
问题 I'm on macOS 10.12. mongod --version db version v3.2.8 git version: ed70e33130c977bda0024c125b56d159573dbaf0 OpenSSL version: OpenSSL 1.0.2h 3 May 2016 allocator: system modules: none build environment: distarch: x86_64 target_arch: x86_64 When I use a mongorestore: mongorestore --drop --db mydatabase /path/to/mongodump The import starts but it crashes 90% of time: fatal error: unexpected signal during runtime execution [signal 0xb code=0x1 addr=0x697d5fa61ae3 pc=0x40d9e00] goroutine 46

mongorestore random crash (fatal error)

邮差的信 提交于 2019-12-05 04:36:37
I'm on macOS 10.12. mongod --version db version v3.2.8 git version: ed70e33130c977bda0024c125b56d159573dbaf0 OpenSSL version: OpenSSL 1.0.2h 3 May 2016 allocator: system modules: none build environment: distarch: x86_64 target_arch: x86_64 When I use a mongorestore: mongorestore --drop --db mydatabase /path/to/mongodump The import starts but it crashes 90% of time: fatal error: unexpected signal during runtime execution [signal 0xb code=0x1 addr=0x697d5fa61ae3 pc=0x40d9e00] goroutine 46 [running]: runtime.throw(0x4683ea0, 0x2a) /usr/local/Cellar/go/1.6.2/libexec/src/runtime/panic.go:547 +0x90

drop whole database within a single command of restoring the dump of mongodb

一世执手 提交于 2019-12-02 05:00:49
问题 I am trying to restore the directory dump of mongodb. i am doing mongorestore --db mydb --drop path/to/mydb/dump But both does not able to restore the state of my dump. Any new records are visible even after restoring the db. But no error is shown on console. 回答1: I didn't see an answer and I had the same question today. You can drop the database before with: use <db> db.dropDatabase() Or you can only drop the collection with: db.<collection>.drop() The problem with your command could be that

drop whole database within a single command of restoring the dump of mongodb

寵の児 提交于 2019-12-01 23:05:03
I am trying to restore the directory dump of mongodb. i am doing mongorestore --db mydb --drop path/to/mydb/dump But both does not able to restore the state of my dump. Any new records are visible even after restoring the db. But no error is shown on console. I didn't see an answer and I had the same question today. You can drop the database before with: use <db> db.dropDatabase() Or you can only drop the collection with: db.<collection>.drop() The problem with your command could be that something misses, like the database which you authenticate against or the user or maybe another thing. In

MongoDb: How to import dump data from .gz file?

故事扮演 提交于 2019-12-01 04:02:19
I want to import dump data from my .gz file. Location of file is home/Alex/Documents/Abc/dump.gz and the name of db is "Alex" . I have tried mongorestore --gzip --db "Alex" /home/Alex/Documents/Abc/dump.gz But it shows error: 2018-10-31T12:54:58.359+0530 the --db and --collection args should only be used when restoring from a BSON file. Other uses are deprecated and will not exist in the future; use --nsInclude instead 2018-10-31T12:54:58.359+0530 Failed: file /home/Alex/Documents/Abc/dump.gz does not have .bson extension. How can I import it? Dump command: mongodump --host localhost:27017 -

MongoDb: How to import dump data from .gz file?

不打扰是莪最后的温柔 提交于 2019-12-01 01:21:38
问题 I want to import dump data from my .gz file. Location of file is home/Alex/Documents/Abc/dump.gz and the name of db is "Alex" . I have tried mongorestore --gzip --db "Alex" /home/Alex/Documents/Abc/dump.gz But it shows error: 2018-10-31T12:54:58.359+0530 the --db and --collection args should only be used when restoring from a BSON file. Other uses are deprecated and will not exist in the future; use --nsInclude instead 2018-10-31T12:54:58.359+0530 Failed: file /home/Alex/Documents/Abc/dump.gz

MongoDB dump from 3.2, restore with 3.4, error index safe = null

Deadly 提交于 2019-11-30 12:43:28
问题 I get the following error (dump MongoDB 3.2) (restore MongoDB 3.4): Failed: ngivr-dev.ledgerhelpers: error creating indexes for ngivr-dev.ledgerhelpers: **createIndex error:** **The field 'safe' is not valid for an index specification.** Specification: **{ unique: true, name: "ledgerId_1", safe: null, ns: "ngivr-dev.ledgerhelpers", background: true, key: { ledgerId: 1 } }** Looks like the safe index is null. But how can i use it with MongoDB 3.4? 3.2 is ok. 回答1: safe=true is not an index

MongoDB dump from 3.2, restore with 3.4, error index safe = null

时间秒杀一切 提交于 2019-11-30 02:57:33
I get the following error (dump MongoDB 3.2) (restore MongoDB 3.4): Failed: ngivr-dev.ledgerhelpers: error creating indexes for ngivr-dev.ledgerhelpers: **createIndex error:** **The field 'safe' is not valid for an index specification.** Specification: **{ unique: true, name: "ledgerId_1", safe: null, ns: "ngivr-dev.ledgerhelpers", background: true, key: { ledgerId: 1 } }** Looks like the safe index is null. But how can i use it with MongoDB 3.4? 3.2 is ok. safe=true is not an index specification. In previous versions of MongoDB, lower than 3.4, extra indexes specifications can be added. Those

Can mongorestore take a single url argument instead of separate arguments?

两盒软妹~` 提交于 2019-11-29 06:55:54
If I have a mongo database URL of the following format mongodb://someUsername:somePassword@some.server.com:27017/some_collection Is there an easy way to give this to mongorestore without having to do mongorestore -u someUsername -p somePassword -h some.server.com:27017 -db some_collection /path/to/dump The reason I ask is because meteor mongo --url gives back a url of that form (and it looks like a standardized url format) but it expires in one minute . Because the password and host can be pretty long, it's hit or miss whether I can copy the parameters over (correctly) in one minute, and

Mongorestore, from meteor production server to local

混江龙づ霸主 提交于 2019-11-28 19:19:31
I've found plenty of good instructions on how to use mongodump and mongorestore, to back up my meteor production server and restore the backup if need be: meteor mongo --url myApp.meteor.com mongodump -u client -h production-db-b2.meteor.io:27017 -d myApp_meteor_com -out dump/2014_10_21 -p [password from meteor mongo --url] mongorestore -u client -h production-db-b2.meteor.io:27017 -d myApp_meteor_com dump/2014_10_21_v2/myApp_meteor_com -p [password from meteor mongo --url] What I haven't found is an explanation of is how to restore a backup-dump to my local meteor app. I have a mongodump