On 06/25/2013 11:45 AM, Joao Eduardo Luis wrote: >> On mon a I see: >> >> # ceph --admin-daemon /run/ceph/ceph-mon.a.asok mon_status >> { "name": "a", >> "rank": 0, >> "state": "probing", >> "election_epoch": 1, >> "quorum": [], >> "outside_quorum": [ >> "a"], >> "extra_probe_peers": [], >> "monmap": { "epoch": 14, >> "fsid": "61ebf2c4-5290-4fbb-8a84-bc8797351bf8", >> "modified": "2013-06-25 10:00:14.004097", >> "created": "2013-06-24 15:06:08.472355", >> "mons": [ >> { "rank": 0, >> "name": "a", >> "addr": "46.20.16.21:6789\/0"}, >> { "rank": 1, >> "name": "b", >> "addr": "46.20.16.22:6789\/0"}]}} > > What happens when you run the same command for mon.b ? # ceph mon add b x.y.z.b:6789 ^Z [1]+ Stopped ceph mon add b x.y.z.b:6789 root@rd-clusternode22:/etc/ceph# bg [1]+ ceph mon add b x.y.x.b:6789 & # 2013-06-25 11:48:56.136659 7f5b419a3700 0 monclient: hunting for new mon # ceph --admin-daemon /run/ceph/ceph-mon.b.asok mon_status connect to /run/ceph/ceph-mon.a.asok failed with (2) No such file or directory it can't be started and isn't running, so I guess that's why we wouldn't get anything from socket back here... > -Joao wogri_risc _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com