Wow... disregard this, I figured it out.
Overly restrictive iptables rules permitted incoming traffic from lo,
but outgoing traffic "to" lo was blocked... *facepalm*
On 13/10/2014 15:09, Marc wrote:
> Hi,
>
> I've deployed a number of clusters before on debian boxes, but now I
> have to create one on centos boxes (not my choice) and I've run into a
> road block.
>
> I have started with the usual steps:
>
> - complete preflight
> - ceph-deploy new node01
> - ceph-deploy install node01
> - ceph-deploy mon create-initial node01
>
> This one completes, but ceph-deploy then fails to collect the keys. More
> specifically the client.admin.keyring.
>
> I suspect this process here is hanging:
>
> root 845 835 0 15:01 pts/0 00:00:00 python /usr/bin/ceph
> --cluster=ceph --name=mon.
> --keyring=/var/lib/ceph/mon/ceph-node01/keyring auth get-or-create
> client.admin mon allow * osd allow * mds allow
>
>
> Is there any way for me to determine why? Since I don't have a
> client.admin.keyring yet, I can't use normal ceph commands at this
> point, but mon_status queried via socket looks fine:
>
> { "name": "node01",
> "rank": 0,
> "state": "leader",
> "election_epoch": 2,
> "quorum": [
> 0],
> "outside_quorum": [],
> "extra_probe_peers": [],
> "sync_provider": [],
> "monmap": { "epoch": 1,
> "fsid": "172254a8-*SNIP*",
> "modified": "0.000000",
> "created": "0.000000",
> "mons": [
> { "rank": 0,
> "name": "node01",
> "addr": "10.0.0.1:6789\/0"}]}}
>
> Almost forgot: this is .80.6
>
> Regards,
> Marc
> _______________________________________________
> ceph-users mailing list
> [email protected]
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
