On Wed, 24 Jul 2013, Dan van der Ster wrote:
> On Wednesday, July 24, 2013 at 7:19 AM, Sage Weil wrote:
> On Wed, 24 Jul 2013, S?bastien RICCIO wrote:
>
> Hi! While trying to install ceph using ceph-deploy the monitors
> nodes are
> stuck waiting on this process:
> /usr/bin/python /usr/sbin/ceph-create-keys -i a (or b or c)
>
> I tried to run mannually the command and it loops on this:
> connect to /var/run/ceph/ceph-mon.a.asok failed with (2) No such
> file or
> directory
> INFO:ceph-create-keys:ceph-mon admin socket not ready yet.
> But the existing sock on the nodes are
> /var/run/ceph/ceph-mon.ceph01.asok
>
> Is that a bug in ceph-deploy or maybe my config file is wrong ?
>
>
> It's the config file. You no longer need to (or should) enumerate the
> daemons in the config file; the sysvinit/upstart scripts find them in
> /var/lib/ceph/{osd,mon,mds}/*. See below:
>
> If we don't enumerate the osds, how does the init script know
> which "devs" to mount for each daemon?
If you use the ceph-deploy/ceph-disk tools, we partition the disk and mark
the GPT partition types so that the udev rules mount them for you. (This
also lets you swap disks between machines without any futzing with
configs.)
> And I guess it doesn't apply to clients' copy of ceph.conf, where all the
> mons should be enumerated?
You can do the mon sections with mon addr, or you can just list them on a
single config line like
[global]
mon host = host1, host2, host3
or even
[global]
mons.foo.com
where that dns entry has multiple A records.
sage_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
