Re: stuck ceph-deploy mon create-initial / giant

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 24 Feb 2015 11:17:22 +0100 Loic Dachary wrote:

> 
> 
> On 24/02/2015 09:58, Stephan Seitz wrote:
> > Hi Loic,
> > 
> > this is the content of our ceph.conf
> > 
> > [global]
> > fsid = 719f14b2-7475-4b25-8c5f-3ffbcf594d13
> > mon_initial_members = ceph1, ceph2, ceph3
> > mon_host = 192.168.10.107,192.168.10.108,192.168.10.109
> > auth_cluster_required = cephx
> > auth_service_required = cephx
> > auth_client_required = cephx
> > filestore_xattr_use_omap = true
> > osd pool default size = 2
> > public network = 192.168.10.0/24
> > cluster networt = 192.168.108.0/24
> 
> s/networt/network/ ?
> 

If this really should turn out to be the case, it is another painfully
obvious reason why I proposed to provide full config parser output in
the logs when in default debugging level.

Stuff like this or the lack of picking up configuration statements would
be immediately visible. 

Christian

> > 
> > where public network is 10GBE native and cluster network a tagged VLAN
> > on a lacp/802.3ad bond.
> > 
> > 
> > 
> > 
> > Am Montag, den 23.02.2015, 23:24 +0100 schrieb Loic Dachary:
> >> Hi Stephan,
> >>
> >> Could you share the /etc/ceph/ceph.conf content ? Maybe
> >> ceph-create-keys cannot reach the monitor ?
> >>
> >> Cheers
> >>
> >> On 23/02/2015 22:53, Stephan Seitz wrote:
> >>> Hi all,
> >>>
> >>> I'm currently facing a strange problem when deploying giant on
> >>> Ubuntu 14.04. Following the docs, and reaching to
> >>> ceph-deploy mon create-initial
> >>> on the three mon hosts leads to every single mon stuck with a
> >>> companion ceph-create-keys waiting forever.
> >>> ceph-deploy quits after waiting for mon-qorum without success. Say:
> >>> with 
> >>> error: for each mon.
> >>> An strace shows repetively the very same bulk, with one line stating
> >>> the mon state in "pending".
> >>> Network has been double-checked. netstat / lsof shows "established"
> >>> TCP connection between the mons.
> >>>
> >>> Trying to fiddle around the quorum and starting the cluster with
> >>> only one mon, didn't help either. It behaves in the very same way:
> >>> Having the 
> >>> mon stuck and the ceph-create-keys waiting forever.
> >>>
> >>> Could someone please shed some light, what this problem could be
> >>> caused by?
> >>> Except for deploying the first time giant, I didn't face that problem
> >>> on 
> >>> former installations.
> >>>
> >>> Thanks in advance,
> >>>
> >>> - Stephan
> >>>
> >>
> > 
> 


-- 
Christian Balzer        Network/Systems Engineer                
chibi@xxxxxxx   	Global OnLine Japan/Fusion Communications
http://www.gol.com/
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux