Hi guys. I have one crash - containerized cluster - which upon start logs: ... INFO:ceph-crash:pinging cluster to exercise our key 2025-08-18T14:59:59.663+0000 7fe9106bb640 -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 2025-08-18T14:59:59.663+0000 7fe9106bb640 -1 AuthRegistry(0x7fe908069670) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-18T14:59:59.664+0000 7fe9106bb640 -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 2025-08-18T14:59:59.664+0000 7fe9106bb640 -1 AuthRegistry(0x7fe9106b9ff0) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-18T14:59:59.665+0000 7fe90e430640 -1 monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [1] 2025-08-18T14:59:59.665+0000 7fe90dc2f640 -1 monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [1] In that 'crash' container I have: -> $ ll /etc/ceph/ total 16 -rw-------. 1 ceph ceph  81 Aug  6 13:26 ceph.client.crash.podster1.keyring -rw-------. 1 ceph ceph 253 Aug  6 13:26 ceph.conf -rw-------. 1 root root 151 Aug 18 04:20 ceph.keyring -rw-r--r--. 1 root root  92 Jul 17 03:53 rbdmap then: -> $ ceph auth get client.admin [client.admin]     key = AQD....     caps mds = "allow *"     caps mgr = "allow *"     caps mon = "allow *"     caps osd = "allow *" which key is in: /etc/ceph/ceph.keyring on this 'crash' What is happening here can anybody suggest/tell? Other 'crashes' remain that-error-free - but I wonder if that is only because they have had nothing to do yet. This one 'crash' has - on the same node - monitor failing. many thanks, L.