Too bad. :-/ Could you increase the debug log level to 20? Maybe it
gets a bit clearer where exactly it fails.
Just to understand the current situation, you did reduce the monmap to
1 (mon3), then you tried the same with mon2. Because when you write:
I'm guessing that mon2 is only "running" because it's waiting for a
response from the paxos election (and none of the others is
responding by now).
it reads like you did try to start all of them again. If you only have
mon in the monmap, there's no waiting for an election.
Zitat von Miles Goodhew <c...@m0les.com>:
All,
An update: I tried editing the monmap on mon3 to be just [mon3]
and starting the mon daemon there. It died immediately with the
"maybe_resize_cluster" method exception mentioned before. I then
tried the same trick on mon2 (that's the daemon that would stay up
if all 3 are started) and got the same behaviour.
I'm guessing that mon2 is only "running" because it's waiting for
a response from the paxos election (and none of the others is
responding by now). If we remove that block, it goes straight to the
"maybe_resize_cluster" call and gets the same "out of range"
exception.
I suspect the issue is with whatever "max_mds" is and what is "out
of range".
Also, I discovered "ceph-kvstore-tool", which makes looking in the
leveldb a lot easier.
Thanks,
M0les.
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
