Hi,
there's a profile "crash" for that. In a lab setup with Nautilus
thre's one crash client with these caps:
admin:~ # ceph auth get client.crash
[client.crash]
key = ****
caps mgr = "allow profile crash"
caps mon = "allow profile crash"
On a Octopus cluster deployed by cephadm each host gets its own crash client:
ses7-host1:~ # ceph auth ls | grep crash
installed auth entries:
client.crash.ses7-host1
caps: [mgr] profile crash
caps: [mon] profile crash
client.crash.ses7-host2
caps: [mgr] profile crash
caps: [mon] profile crash
client.crash.ses7-host3
caps: [mgr] profile crash
caps: [mon] profile crash
client.crash.ses7-host4
caps: [mgr] profile crash
caps: [mon] profile crash
But the capabilities are the same.
Regards,
Eugen
Zitat von Burkhard Linke <Burkhard.Linke@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>:
Hi,
I just stumpled over some log messages regarding ceph-crash:
May 10 09:32:19 bigfoot60775 ceph-crash[2756]:
WARNING:ceph-crash:post
/var/lib/ceph/crash/2022-05-10T07:10:55.837665Z_7f3b726e-0368-4149-8834-6cafd92fb13f as client.admin failed: b'2022-05-10T09:32:19.099+0200 7f911ad92700 -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\n2022-05-10T09:32:19.099+0200 7f911ad92700 -1 AuthRegistry(0x7f911405b178) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,, disabling cephx\n2022-05-10T09:32:19.107+0200 7f9119b30700 -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\n2022-05-10T09:32:19.107+0200 7f9119b30700 -1 AuthRegistry(0x7f91140609d0) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,, disabling cephx\n2022-05-10T09:32:19.107+0200 7f9119b307
00 -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\n2022-05-10T09:32:19.107+0200 7f9119b30700 -1 AuthRegistry(0x7f9119b2efe0) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,, disabling cephx\n[errno 2] RADOS object not found (error connecting to the
cluster)\n'
This cluster is a manual setup, no cephadm or other stuff. We do not
deploy the admin key to the OSD nodes unless absolutely necessary...
How can I configure a separate cephx user for ceph-crash? Which
capabilities are required for that user?
Regards,
Burkhard
_______________________________________________
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
