Hi,
I checked the behaviour on Octopus, Pacific and Quincy, I can confirm.
I don't have the time to dig deeper right now, but I'd suggest to open
a tracker issue.
Thanks,
Eugen
Zitat von Jan Kasprzak <kas@xxxxxxxxxx>:
Hello, Ceph users,
what is the correct location of keyring for ceph-crash?
I tried to follow this document:
https://docs.ceph.com/en/latest/mgr/crash/
# ceph auth get-or-create client.crash mon 'profile crash' mgr
'profile crash' > /etc/ceph/ceph.client.crash.keyring
and copy this file to all nodes. When I run ceph-crash.service on the node
where client.admin.keyring is available, it works. But on the rest of nodes,
it tries to access the admin keyring anyway. Journalctl -u ceph-crash
says this:
Jan 18 18:03:35 my.node.name systemd[1]: Started Ceph crash dump collector.
Jan 18 18:03:35 my.node.name ceph-crash[2973164]:
INFO:ceph-crash:pinging cluster to exercise our key
Jan 18 18:03:35 my.node.name ceph-crash[2973166]:
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-crash[2973166]:
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-crash[2973166]:
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-crash[2973166]:
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-crash[2973166]:
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-crash[2973166]:
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-crash[2973166]: [errno 2] RADOS
object not found (error connecting to the cluster)
Jan 18 18:03:35 my.node.name ceph-crash[2973164]:
INFO:ceph-crash:monitoring path /var/lib/ceph/crash, delay 600s
Is the documentation outdated, or am I doing anything wrong? Thanks for
any hint. This is non-containerized Ceph 18.2.1 on AlmaLinux 9.
-Yenya
--
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| https://www.fi.muni.cz/~kas/ GPG: 4096R/A45477D5 |
We all agree on the necessity of compromise. We just can't agree on
when it's necessary to compromise. --Larry Wall
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
