On Sun, Aug 4, 2013 at 12:16 PM, Sage Weil wrote:
> It looks like the auth state wasn't trimmed properly. It also sort of
> looks like you aren't using authentication on this cluster... is that
> true? (The keyring file was empty.)
>
> Yes, your're right, I disable auth. It's just a personal cl
It looks like the auth state wasn't trimmed properly. It also sort of
looks like you aren't using authentication on this cluster... is that
true? (The keyring file was empty.)
This looks like a trim issue, but I don't remember what all we fixed since
.1.. that was a while ago! We certainly h
On Sun, Aug 4, 2013 at 12:13 AM, Sage Weil wrote:
> On Sat, 3 Aug 2013, Yu Changyuan wrote:
> > I run a tiny ceph cluster with only one monitor. After a reboot the
> system,
> > the monitor refuse to start.
> > I try to start ceph-mon manually with command 'ceph -f -i a', below is
> > first few
On Fri, 2 Aug 2013, Kevin Weiler wrote:
> I'm having some trouble bootstrapping my monitors using this page as a
> guide:
>
> http://ceph.com/docs/next/dev/mon-bootstrap/
>
> I can't seem to authenticate to my monitors with client.admin after I've
> created them and started them:
>
You also nee
On Sat, 3 Aug 2013, Yu Changyuan wrote:
> I run a tiny ceph cluster with only one monitor. After a reboot the system,
> the monitor refuse to start.
> I try to start ceph-mon manually with command 'ceph -f -i a', below is
> first few lines of the output:
>
> starting mon.a rank 0 at 192.168.1.10:
I run a tiny ceph cluster with only one monitor. After a reboot the system,
the monitor refuse to start.
I try to start ceph-mon manually with command 'ceph -f -i a', below is
first few lines of the output:
starting mon.a rank 0 at 192.168.1.10:6789/0 mon_data
/var/lib/ceph/mon/ceph-a fsid 554bee
