adding shard addshard42
2012-07-24 21:08:22 EDT	
 m30999| Tue Jul 24 21:08:20 [conn1] starting new replica set monitor for replica set addshard42 with seed of domU-12-31-39-01-70-B4:31202
 m30999| Tue Jul 24 21:08:20 [conn1] successfully connected to seed domU-12-31-39-01-70-B4:31202 for replica set addshard42
 m31202| Tue Jul 24 21:08:20 [conn5] end connection 10.255.119.66:36504 (4 connections now open)
 m31200| Tue Jul 24 21:08:20 [slaveTracking] build index local.slaves { _id: 1 }
 m31202| Tue Jul 24 21:08:20 [initandlisten] connection accepted from 10.255.119.66:36504 #5 (5 connections now open)
 m31200| Tue Jul 24 21:08:20 [slaveTracking] build index done.  scanned 0 total records. 0 secs
 m31200| Tue Jul 24 21:08:22 [rsHealthPoll] replSet member domU-12-31-39-01-70-B4:31201 is now in state SECONDARY
 m30999| Tue Jul 24 21:08:22 [conn1] warning: No primary detected for set addshard42
 m31201| Tue Jul 24 21:08:20 [rsSync] replSet SECONDARY
2012-07-24 21:08:24 EDT	
 m30999| Tue Jul 24 21:08:22 [conn1] All nodes for set addshard42 are down. This has happened for 1 checks in a row. Polling will stop after 29 more failed checks
 m30999| Tue Jul 24 21:08:22 [Balancer] distributed lock 'balancer/domU-12-31-39-01-70-B4:30999:1343178434:1804289383' acquired, ts : 500f47063d01c6e816bb4fc4
 m30999| Tue Jul 24 21:08:22 [conn1] replica set monitor for replica set addshard42 started, address is addshard42/
 m30999| Tue Jul 24 21:08:22 [Balancer] distributed lock 'balancer/domU-12-31-39-01-70-B4:30999:1343178434:1804289383' unlocked. 
 m31102| Tue Jul 24 21:08:23 [conn7] end connection 10.255.119.66:55945 (5 connections now open)
 m31102| Tue Jul 24 21:08:23 [initandlisten] connection accepted from 10.255.119.66:52642 #9 (6 connections now open)
 m30999| Tue Jul 24 21:08:24 [conn1] warning: No primary detected for set addshard42
 m30999| Tue Jul 24 21:08:24 [conn1] deleting replica set monitor for: addshard42/
 m30999| Tue Jul 24 21:08:24 [conn1] addshard request { addshard: "addshard42/domU-12-31-39-01-70-B4:31202" } failed: couldn't connect to new shard socket exception
 m31202| Tue Jul 24 21:08:22 [rsHealthPoll] replSet member domU-12-31-39-01-70-B4:31201 is now in state SECONDARY
Tue Jul 24 21:08:24 uncaught exception: command { "addshard" : "addshard42/domU-12-31-39-01-70-B4:31202" } failed: { "ok" : 0, "errmsg" : "couldn't connect to new shard socket exception" }
 m30000| Tue Jul 24 21:08:24 got signal 15 (Terminated), will terminate after current cmd ends
failed to load: /mnt/slaves/Linux_32bit/mongo/jstests/sharding/addshard4.js