Hey folks,
I've just done a brand new install of 0.67.2 on a cluster of Calxeda nodes.
I have one particular monitor that number joins the quorum when I restart
the node. Looks to me like it has something to do with the "create-keys"
task, which never seems to finish:
root 1240 1 4 13:03 ? 00:00:02 /usr/bin/ceph-mon
--cluster=ceph -i n24 -f
root 1244 1 0 13:03 ? 00:00:00 /usr/bin/python
/usr/sbin/ceph-create-keys --cluster=ceph -i n24
I don't see that task on my other monitors. Additionally, that task is
periodically query the monitor status:
root 1240 1 2 13:03 ? 00:00:02 /usr/bin/ceph-mon
--cluster=ceph -i n24 -f
root 1244 1 0 13:03 ? 00:00:00 /usr/bin/python
/usr/sbin/ceph-create-keys --cluster=ceph -i n24
root 1982 1244 15 13:04 ? 00:00:00 /usr/bin/python
/usr/bin/ceph --cluster=ceph --admin-daemon=/var/run/ceph/ceph-mon.n24.asok
mon_status
Checking that status myself, I see:
# ceph --cluster=ceph --admin-daemon=/var/run/ceph/ceph-mon.n24.asok
mon_status
{ "name": "n24",
"rank": 2,
"state": "probing",
"election_epoch": 0,
"quorum": [],
"outside_quorum": [
"n24"],
"extra_probe_peers": [],
"sync_provider": [],
"monmap": { "epoch": 2,
"fsid": "f0b0d4ec-1ac3-4b24-9eab-c19760ce4682",
"modified": "2013-08-23 12:55:34.374650",
"created": "0.000000",
"mons": [
{ "rank": 0,
"name": "n0",
"addr": "10.0.1.0:6789\/0"},
{ "rank": 1,
"name": "n12",
"addr": "10.0.1.12:6789\/0"},
{ "rank": 2,
"name": "n24",
"addr": "0.0.0.0:6810\/0"}]}}
Any ideas what is going on here? I don't see anything useful in
/var/log/ceph/ceph-mon.n24.log
Thanks,
- Travis
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
