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?
And I guess it doesn't apply to clients' copy of ceph.conf, where all the mons
should be enumerated?
Thanks, Dan
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
