Hello, same here. My fix was to examine the keyring file in the misbehaving server and compare to a different server, I found the file had the key but was missing: caps mgr = "profile crash" caps mon = "profile crash" I added that back in and now its OK. /var/lib/ceph/<your ceph ID>./crash.node1/keyring No idea how this happened On Fri, Jul 3, 2020 at 11:47 PM <DHilsbos@xxxxxxxxxxxxxx> wrote: > > Biohazard; > > This looks like a fairly simple authentication issue. It looks like the keyring(s) available to the command don't contain a key which meets the commands needs. > > Have you verified the presence and accuracy of your keys? > > Thank you, > > Dominic L. Hilsbos, MBA > Director - Information Technology > Perform Air International Inc. > DHilsbos@xxxxxxxxxxxxxx > www.PerformAir.com > > > > -----Original Message----- > From: biohazd@xxxxxxxxx [mailto:biohazd@xxxxxxxxx] > Sent: Friday, July 3, 2020 2:29 AM > To: ceph-users@xxxxxxx > Subject: Module 'cephadm' has failed: auth get failed: failed to find client.crash.ceph0-ote in keyring retval: > > anyone seen this error on the new Ceph 15.2.4 cluster using cpehadm to manage it ? > > Module 'cephadm' has failed: auth get failed: failed to find client.crash.ceph0-ote in keyring retval: > _______________________________________________ > 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 _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |