Project

General

Profile

Actions
Copy link

Bug #64102

open

Ceph-crash keyring name/location

Added by Jan Kasprzak 4 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
v18.2.1
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

According to the docs (https://docs.ceph.com/en/latest/mgr/crash/), ceph-crash should use ceph.client.crash.keyring. However, for me ceph-crash works only on nodes where ceph.client.admin.keyring is also present.

I created the keyring as described in the docs:

  1. ceph auth get-or-create client.crash mon 'profile crash' mgr 'profile crash' > /etc/ceph/ceph.client.crash.keyring

and copied /etc/ceph/ceph.client.crash.keyring to all nodes. When I run "systemctl restart ceph-crash", it seems it tries to access the client.admin.keyring instead. Journalctl -u ceph-crash says:

Jan 18 18:03:35 my.node.name systemd1: Started Ceph crash dump collector.
Jan 18 18:03:35 my.node.name ceph-crash2973164: INFO:ceph-crash:pinging cluster to exercise our key
Jan 18 18:03:35 my.node.name ceph-crash2973166: 2024-01-18T18:03:35.786+0100 7eff34016640 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory
Jan 18 18:03:35 my.node.name ceph-crash2973166: 2024-01-18T18:03:35.786+0100 7eff34016640 -1 AuthRegistry(0x7eff2c063ce8) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx
Jan 18 18:03:35 my.node.name ceph-crash2973166: 2024-01-18T18:03:35.787+0100 7eff34016640 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory
Jan 18 18:03:35 my.node.name ceph-crash2973166: 2024-01-18T18:03:35.787+0100 7eff34016640 -1 AuthRegistry(0x7eff2c067de0) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx
Jan 18 18:03:35 my.node.name ceph-crash2973166: 2024-01-18T18:03:35.788+0100 7eff34016640 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory
Jan 18 18:03:35 my.node.name ceph-crash2973166: 2024-01-18T18:03:35.788+0100 7eff34016640 -1 AuthRegistry(0x7eff340150c0) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx
Jan 18 18:03:35 my.node.name ceph-crash2973166: [errno 2] RADOS object not found (error connecting to the cluster)
Jan 18 18:03:35 my.node.name ceph-crash2973164: INFO:ceph-crash:monitoring path /var/lib/ceph/crash, delay 600s

So either the docs are wrong, or there is a bug in ceph-crash, where it looks for client.admin.keyring instead client.crash.keyring.
My cluster currently runs non-containerized Ceph 18.2.1 on AlmaLinux 9.

Previously reported here: https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/thread/5JYWVOK3NFGXUOBNJFL6EED7YW32DXLY/

Thanks!

-Yenya

No data to display

Actions
Copy link

Also available in: Atom PDF