On 17/11/2017 09:40, Yan, Zheng wrote:
On Fri, Nov 17, 2017 at 4:37 PM, Willem Jan Withagen <wjw@xxxxxxxxxxx> wrote:
On 16/11/2017 13:08, Yan, Zheng wrote:
On Thu, Nov 16, 2017 at 3:06 AM, Willem Jan Withagen <wjw@xxxxxxxxxxx>
wrote:
After a server restart my MDS does not want to start, and it looks like
keys
don't match or something?
This is de MDS log:
2017-11-15 20:03:18.180242 9e0e000 10 mds.a MDSDaemon::ms_get_authorizer
type=mon
2017-11-15 20:03:18.181387 9e0f200 10 cephx: set_have_need_key no handler
for service mon
2017-11-15 20:03:18.181394 9e0f200 10 cephx: set_have_need_key no handler
for service mds
2017-11-15 20:03:18.181396 9e0f200 10 cephx: set_have_need_key no handler
for service osd
2017-11-15 20:03:18.181399 9e0f200 10 cephx: set_have_need_key no handler
for service mgr
2017-11-15 20:03:18.181401 9e0f200 10 cephx: set_have_need_key no handler
for service auth
2017-11-15 20:03:18.181402 9e0f200 10 cephx: validate_tickets want 55
have 0
need 55
2017-11-15 20:03:18.181414 9e0f200 10 cephx client: handle_response ret =
0
2017-11-15 20:03:18.181417 9e0f200 10 cephx client: got initial server
challenge 7d0dda00ee4847b8
2017-11-15 20:03:18.181420 9e0f200 10 cephx client: validate_tickets:
want=55 need=55 have=0
2017-11-15 20:03:18.181424 9e0f200 10 cephx: set_have_need_key no handler
for service mon
2017-11-15 20:03:18.181426 9e0f200 10 cephx: set_have_need_key no handler
for service mds
2017-11-15 20:03:18.181427 9e0f200 10 cephx: set_have_need_key no handler
for service osd
2017-11-15 20:03:18.181428 9e0f200 10 cephx: set_have_need_key no handler
for service mgr
2017-11-15 20:03:18.181429 9e0f200 10 cephx: set_have_need_key no handler
for service auth
2017-11-15 20:03:18.181430 9e0f200 10 cephx: validate_tickets want 55
have 0
need 55
2017-11-15 20:03:18.181433 9e0f200 10 cephx client: want=55 need=55
have=0
2017-11-15 20:03:18.181439 9e0f200 10 cephx client: build_request
2017-11-15 20:03:18.181451 9e0f200 20 cephx client: no secret found for
entity: mds.a
2017-11-15 20:03:18.182114 9e0f200 10 cephx client: handle_response ret =
-22
2017-11-15 20:03:18.182214 9b54480 -1 mds.a ERROR: failed to
authenticate:
(22) Invalid argument
2017-11-15 20:03:18.182253 9b54480 1 mds.a suicide. wanted state
up:boot
2017-11-15 20:03:18.182401 9b54480 10 mds.beacon.a set_want_state:
up:boot
-> down:dne
Please check if content of /var/lib/ceph/mds/ceph-a/keyring is
correct. I got similar error after truncating that file
Right so how do I do that.
One way or another I have a hard time getting my head wrapped around the
auth-model that ceph uses...
ceph auth get mds.a | head -n 2 > /var/lib/ceph/mds/ceph-a/keyring
Great, thanx....
I do have a different key in mds/mds.a/keyring from what ceph itself thinks.
Turns out that my cluster build script is doing something wrong to get
the key.
--WjW
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
