Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
2.2.0
-
None
-
None
-
Ubuntu 10.04 LTS, mongodb 2.2.0
-
ALL
Description
Below is shell session which shows the failure. Note that mongorestore lists
127.0.0.1:27019 as primary and fails to find a master in the next line.
user@host:~$ mongorestore --host 127.0.0.1:27019,127.0.0.1:27018 -d mydb --drop -c User mongo-dump/mydb/User.bson
Mon Sep 24 16:37:31 warning: replica set name empty, first node: 127.0.0.1:27019
Mon Sep 24 16:37:31 starting new replica set monitor for replica set with seed of 127.0.0.1:27019,127.0.0.1:27018
Mon Sep 24 16:37:31 successfully connected to seed 127.0.0.1:27019 for replica set
Mon Sep 24 16:37:31 warning: node: 127.0.0.1:27019 isn't a part of set: ismaster:
Mon Sep 24 16:37:31 successfully connected to seed 127.0.0.1:27018 for replica set
Mon Sep 24 16:37:31 warning: node: 127.0.0.1:27018 isn't a part of set: ismaster:
Mon Sep 24 16:37:33 warning: No primary detected for set
Mon Sep 24 16:37:33 All nodes for set are down. This has happened for 1 checks in a row. Polling will stop after 29 more failed checks
Mon Sep 24 16:37:33 replica set monitor for replica set started, address is
Mon Sep 24 16:37:33 [ReplicaSetMonitorWatcher] starting
Mon Sep 24 16:37:35 warning: No primary detected for set
couldn't connect to [127.0.0.1:27019,127.0.0.1:27018] connect failed to set 127.0.0.1:27019,127.0.0.1:27018
Logstream::get called in uninitialized state
Mon Sep 24 16:37:35 deleting replica set monitor for:
user@host:~$