Good day! Yep. Noticed this problem too under Debian. It was keys-copy step problem. My mon process was alive. But there were no keys in location so no quorum but 4-5 ceph-create-keys processes. Tried to copy keys manually between all nodes and restarted ceph. This was helpful.
Regards, Artem Silenkov, 2GIS TM. --- 2GIS LLC http://2gis.ru [email protected] gtalk:[email protected] cell:+79231534853 2013/6/19 Gregory Farnum <[email protected]> > On Wed, Jun 19, 2013 at 4:13 AM, Alex Bligh <[email protected]> wrote: > > > > On 19 Jun 2013, at 10:42, James Harper wrote: > > > >> Why are there so many ceph-create-keys processes? Under Debian, every > time I start the mons another ceph-create-keys process starts up. > > > > I've seen these hang around for no particular good reason (no Ubuntu). > It seems to happen when there is some difficulty starting mon services. > Once everything is up and running, it doesn't happen (at least for me). I > never worked out quite what it was, but I think it was something like the > init script starts them, but doesn't kill them under every circumstance > where starting a mon fails. > > Yeah. The ceph-create-keys process is started whenever the monitor is > and is responsible for (you guessed it!) creating local copies of the > bootstrap-osd, admin, etc keys and putting them in the appropriate > location. This requires the local monitor to have joined a cluster, > and if there are issues then ceph-create-keys can't connect and just > hangs around. As you mention, Alex, it would be good if the init > script killed them when the monitor dies and I've created an issue for > that: http://tracker.ceph.com/issues/5397 > -Greg > _______________________________________________ > 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
