Okay then I'd suggest adding keyring to the client section in ceph.conf, it is as simple as keyring = <path_to_keyring>/keyring I hope the client(that the logs complain) is in the keyring file. Do let me know if that works for you, if not, some logs would be good to have to diagnose further. On Fri, Jul 21, 2023 at 7:44 PM Marc <Marc@f1-outsourcing.eu> wrote:

Hi Dhairya,

Yes I have in ceph.conf (only copied the lines below, there are more in these sections). I do not have a keyring path setting in ceph.conf

public network = a.b.c.111/24

[mon] mon host = a.b.c.111,a.b.c.112,a.b.c.113

[mon.a] mon addr = a.b.c.111

[mon.b] mon addr = a.b.c.112

[mon.c] mon addr = a.b.c.113

...

Can you confirm if the mon ip in ceph.conf is correct and is public; also the keyring path is specified correctly?

I need some help understanding this. I have configured nfs-ganesha for cephfs using something like this in ganesha.conf

FSAL { Name = CEPH; User_Id = "testing.nfs"; Secret_Access_Key = "AAAAAAAAAAAAAAA=="; }

But I contstantly have these messages in de ganesha logs, 6x per user_id

auth: unable to find a keyring on /etc/ceph/ceph.client.testing

I thought this was a ganesha authentication order issue, but they[1] say it has to do with ceph. I am still on Nautilus so maybe this has been fixed in newer releases. I still have a hard time understanding why this is an issue of ceph (libraries).

[1] https://github.com/nfs-ganesha/nfs-ganesha/issues/974