mongodb balancer does not move chunks because of obscure error -

mongodb balancer does not move chunks because of obscure error -

after next this guide, on how migrate 3 fellow member replica set shard containing 2 x 3 fellow member replica sets, after sharding 1 of collections nil happened. looking logs, got this:

2014-06-22t16:49:55.467+0000 [balancer] distributed lock 'balancer/vt-mongo-6:27018:1403429707:1804289383' unlocked. 2014-06-22t16:50:01.830+0000 [balancer] distributed lock 'balancer/vt-mongo-6:27018:1403429707:1804289383' acquired, ts : 53a70939025c137381ef2126 2014-06-22t16:50:01.945+0000 [balancer] ns: database.emailevents going move { _id: "database.emailevents-_id_minkey", lastmod: timestamp 1000|0, lastmodepoch: objectid('53a6d810089f342ad32992d4'), ns: "database.emailevents", min: { _id: minkey }, max: { _id: -9199836772564449863 }, shard: "replicaset2" } from: replicaset2 to: replicaset4 tag [] 2014-06-22t16:50:01.945+0000 [balancer] moving chunk ns: database.emailevents moving ( ns: database.emailevents, shard: replicaset2:replicaset2/vt-mongo-4:27017,vt-mongo-5:27017,vt-mongo-6:27017, lastmod: 1|0||000000000000000000000000, min: { _id: minkey }, max: { _id: -9199836772564449863 }) replicaset2:database_replicaset2/vt-mongo-4:27017,vt-mongo-5:27017,vt-mongo-6:27017 -> replicaset4:replicaset4/vt-mongo-1:27017,vt-mongo-2:27017,vt-mongo-3:27017 2014-06-22t16:50:01.954+0000 [balancer] movechunk result: { errmsg: "exception: no primary shard configured db: config", code: 8041, ok: 0.0 } 2014-06-22t16:50:01.955+0000 [balancer] balancer move failed: { errmsg: "exception: no primary shard configured db: config", code: 8041, ok: 0.0 } from: replicaset2 to: replicaset4 chunk: min: { _id: minkey } max: { _id: -9199836772564449863 } 2014-06-22t16:50:02.166+0000 [balancer] distributed lock 'balancer/vt-mongo-6:27018:1403429707:1804289383' unlocked.

generally, error:

result: { errmsg: "exception: no primary shard configured db: config", code: 8041, ok: 0.0 }

is result of machines not beingness able talk one-eachother, isn't case. have manually checked , machines able talk eachother.

mongodb