June 2020 - Support - NFS Ganesha List Archives

3.3 missing nfs-ganesha.service on Debian Buster
by Renaud Fortier 18 Jun '20

18 Jun '20

Hi, The install package for nfs-ganesha 3.3 is missing the systemd unit file nfs-ganesha.service. As a workaround, I will use the file found in the 3.2 package. Renaud

1 0

Re: 3.3 on CentOS7
by Kaleb Keithley 17 Jun '20

17 Jun '20

My comment at the start of this trhead about tagging libntirpc for -release was referring to the ganesha packages in the CentOS Storage SIG. I don't know anything about the ganesha packages that ceph builds. On Wed, Jun 17, 2020 at 11:03 AM Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > I am getting these. Although this is the nfs-ganesha from the ceph > group. I think they use default options of yours. I cannot imagine all > samba rpms are necessary, can they? > > > > ======================================================================== > =================================== > Installing: > nfs-ganesha x86_64 2.7.1-0.1.el7 > CentOS7-custom 605 k > Installing for dependencies: > avahi-libs x86_64 0.6.31-20.el7 > CentOS7 62 k > cups-libs x86_64 1:1.6.3-43.el7 > CentOS7 358 k > gnutls x86_64 3.3.29-9.el7_6 > CentOS7 680 k > gssproxy x86_64 0.7.0-28.el7 > CentOS7 110 k > keyutils x86_64 1.5.8-3.el7 > CentOS7 54 k > libbasicobjects x86_64 0.1.1-32.el7 > CentOS7 26 k > libcollection x86_64 0.7.0-32.el7 > CentOS7 42 k > libevent x86_64 2.0.21-4.el7 > CentOS7 214 k > libini_config x86_64 1.3.1-32.el7 > CentOS7 64 k > libldb x86_64 1.5.4-1.el7 > CentOS7 149 k > libnfsidmap x86_64 0.25-19.el7 > CentOS7 50 k > libntirpc x86_64 1.7.1-0.1.el7 > CentOS7-custom 114 k > libpath_utils x86_64 0.2.1-32.el7 > CentOS7 28 k > libref_array x86_64 0.1.5-32.el7 > CentOS7 27 k > libtalloc x86_64 2.1.16-1.el7 > CentOS7 33 k > libtdb x86_64 1.3.18-1.el7 > CentOS7 49 k > libtevent x86_64 0.9.39-1.el7 > CentOS7 41 k > libverto-libevent x86_64 0.2.5-4.el7 > CentOS7 8.9 k > libwbclient x86_64 4.10.4-11.el7_8 > CentOS7_64-updates 113 k > nettle x86_64 2.7.1-8.el7 > CentOS7 327 k > nfs-utils x86_64 1:1.3.0-0.66.el7 > CentOS7 412 k > pyldb x86_64 1.5.4-1.el7 > CentOS7 49 k > pytalloc x86_64 2.1.16-1.el7 > CentOS7 18 k > python-tdb x86_64 1.3.18-1.el7 > CentOS7 20 k > samba-client-libs x86_64 4.10.4-11.el7_8 > CentOS7_64-updates 5.0 M > samba-common noarch 4.10.4-11.el7_8 > CentOS7_64-updates 212 k > samba-common-libs x86_64 4.10.4-11.el7_8 > CentOS7_64-updates 176 k > samba-libs x86_64 4.10.4-11.el7_8 > CentOS7_64-updates 271 k > trousers x86_64 0.3.14-2.el7 > CentOS7 289 k > > Transaction Summary > ======================================================================== > =================================== > Install 1 Package (+29 Dependent packages) > > > > -----Original Message----- > Cc: bengoa; support > Subject: *****SPAM***** Re: [NFS-Ganesha-Support] Re: 3.3 on CentOS7 > > The only "samba dependency" that I'm aware of is the use of winbind for > krb5/AD support. > > I'm not aware of any way to decouple that from the build, but even if > there is, I'd say it's a pretty key part of NFS, and unless and until > someone rewrites the krb5 support then it's not a something that's going > to change any time soon. > > If you can't get the winbind library without getting all of Samba then > that's a bug in the Samba packaging IMO. > > On Wed, Jun 17, 2020 at 8:26 AM Marc Roos <M.Roos(a)f1-outsourcing.eu> > wrote: > > > > > Please do not package again with the samba dependency. > > > > -----Original Message----- > To: Kaleb Keithley > Cc: support(a)lists.nfs-ganesha.org > Subject: *****SPAM***** [NFS-Ganesha-Support] Re: 3.3 on CentOS7 > > Great, thanks, Kaleb! > > > On Wed, 17 Jun 2020 at 12:13, Kaleb Keithley <kkeithle(a)redhat.com> > > wrote: > > > I just tagged the packages for -release. They should start > propagating to the mirrors soon. > > On Wed, Jun 17, 2020 at 5:24 AM Alberto Bengoa > <bengoa(a)gmail.com> > wrote: > > > Hello guys, > > I'm running a Ganesha Server on CentOS Linux > release 7.8.2003 > (Core) and since the latest version (3.3) I'm unable to get it > updated. > > I'm getting this error message: > > Error: Package: nfs-ganesha-3.3-1.el7.x86_64 > (centos-nfs-ganesha30) > Requires: > libntirpc.so.3.3(NTIRPC_3.3)(64bit) > Error: Package: > nfs-ganesha-gluster-3.3-1.el7.x86_64 > (centos-nfs-ganesha30) > Requires: libntirpc.so.3.3()(64bit) > Error: Package: nfs-ganesha-3.3-1.el7.x86_64 > (centos-nfs-ganesha30) > Requires: libntirpc.so.3.3()(64bit) > Error: Package: nfs-ganesha-utils-3.3-1.el7.x86_64 > (centos-nfs-ganesha30) > Requires: > libntirpc.so.3.3(NTIRPC_3.3)(64bit) > Error: Package: nfs-ganesha-utils-3.3-1.el7.x86_64 > (centos-nfs-ganesha30) > Requires: libntirpc.so.3.3()(64bit) > You could try using --skip-broken to work around > the problem > You could try running: rpm -Va --nofiles > --nodigest > > In fact I don't have libntirpc 3.3 in my system: > > (BETA) root@data2:~$ yum info libntirpc.x86_64 > Loaded plugins: fastestmirror > Loading mirror speeds from cached hostfile > * base: mirrors.clouvider.net > * centos-gluster7: mirrors.clouvider.net > * centos-nfs-ganesha30: mirror.sov.uk.goscomb.net > * epel: ftp.nluug.nl > * extras: mirror.netweaver.uk > * updates: mirror.sov.uk.goscomb.net > Installed Packages > Name : libntirpc > Arch : x86_64 > Version : 3.2 > Release : 1.el7 > Size : 285 k > Repo : installed > From repo : centos-nfs-ganesha30 > [...] > > As you can see, I'm using the repo from > centos-release-nfs-ganesha30-1.0-2.el7.centos.noarch, the latest > one > available for CentOS7. > > Am I doing something wrong or maybe the libntirpc > isn't > available at CentOS Storage SIG repo yet? > > Cheers, > Alberto Bengoa > _______________________________________________ > Support mailing list -- > support(a)lists.nfs-ganesha.org > To unsubscribe send an email to > support-leave(a)lists.nfs-ganesha.org > > > _______________________________________________ > Support mailing list -- support(a)lists.nfs-ganesha.org > To unsubscribe send an email to > support-leave(a)lists.nfs-ganesha.org > > > >

1 0

Re: 3.3 on CentOS7
by Kaleb Keithley 17 Jun '20

17 Jun '20

The only "samba dependency" that I'm aware of is the use of winbind for krb5/AD support. I'm not aware of any way to decouple that from the build, but even if there is, I'd say it's a pretty key part of NFS, and unless and until someone rewrites the krb5 support then it's not a something that's going to change any time soon. If you can't get the winbind library without getting all of Samba then that's a bug in the Samba packaging IMO. On Wed, Jun 17, 2020 at 8:26 AM Marc Roos <M.Roos(a)f1-outsourcing.eu> wrote: > > > Please do not package again with the samba dependency. > > > > -----Original Message----- > To: Kaleb Keithley > Cc: support(a)lists.nfs-ganesha.org > Subject: *****SPAM***** [NFS-Ganesha-Support] Re: 3.3 on CentOS7 > > Great, thanks, Kaleb! > > > On Wed, 17 Jun 2020 at 12:13, Kaleb Keithley <kkeithle(a)redhat.com> > wrote: > > > I just tagged the packages for -release. They should start > propagating to the mirrors soon. > > On Wed, Jun 17, 2020 at 5:24 AM Alberto Bengoa <bengoa(a)gmail.com> > wrote: > > > Hello guys, > > I'm running a Ganesha Server on CentOS Linux release > 7.8.2003 > (Core) and since the latest version (3.3) I'm unable to get it updated. > > I'm getting this error message: > > Error: Package: nfs-ganesha-3.3-1.el7.x86_64 > (centos-nfs-ganesha30) > Requires: libntirpc.so.3.3(NTIRPC_3.3)(64bit) > Error: Package: nfs-ganesha-gluster-3.3-1.el7.x86_64 > (centos-nfs-ganesha30) > Requires: libntirpc.so.3.3()(64bit) > Error: Package: nfs-ganesha-3.3-1.el7.x86_64 > (centos-nfs-ganesha30) > Requires: libntirpc.so.3.3()(64bit) > Error: Package: nfs-ganesha-utils-3.3-1.el7.x86_64 > (centos-nfs-ganesha30) > Requires: libntirpc.so.3.3(NTIRPC_3.3)(64bit) > Error: Package: nfs-ganesha-utils-3.3-1.el7.x86_64 > (centos-nfs-ganesha30) > Requires: libntirpc.so.3.3()(64bit) > You could try using --skip-broken to work around the > problem > You could try running: rpm -Va --nofiles --nodigest > > In fact I don't have libntirpc 3.3 in my system: > > (BETA) root@data2:~$ yum info libntirpc.x86_64 > Loaded plugins: fastestmirror > Loading mirror speeds from cached hostfile > * base: mirrors.clouvider.net > * centos-gluster7: mirrors.clouvider.net > * centos-nfs-ganesha30: mirror.sov.uk.goscomb.net > * epel: ftp.nluug.nl > * extras: mirror.netweaver.uk > * updates: mirror.sov.uk.goscomb.net > Installed Packages > Name : libntirpc > Arch : x86_64 > Version : 3.2 > Release : 1.el7 > Size : 285 k > Repo : installed > From repo : centos-nfs-ganesha30 > [...] > > As you can see, I'm using the repo from > centos-release-nfs-ganesha30-1.0-2.el7.centos.noarch, the latest one > available for CentOS7. > > Am I doing something wrong or maybe the libntirpc isn't > available at CentOS Storage SIG repo yet? > > Cheers, > Alberto Bengoa > _______________________________________________ > Support mailing list -- support(a)lists.nfs-ganesha.org > To unsubscribe send an email to > support-leave(a)lists.nfs-ganesha.org > > > _______________________________________________ > Support mailing list -- support(a)lists.nfs-ganesha.org > To unsubscribe send an email to support-leave(a)lists.nfs-ganesha.org >

2 1

3.3 on CentOS7
by Alberto Bengoa 17 Jun '20

17 Jun '20

Hello guys, I'm running a Ganesha Server on CentOS Linux release 7.8.2003 (Core) and since the latest version (3.3) I'm unable to get it updated. I'm getting this error message: Error: Package: nfs-ganesha-3.3-1.el7.x86_64 (centos-nfs-ganesha30) Requires: libntirpc.so.3.3(NTIRPC_3.3)(64bit) Error: Package: nfs-ganesha-gluster-3.3-1.el7.x86_64 (centos-nfs-ganesha30) Requires: libntirpc.so.3.3()(64bit) Error: Package: nfs-ganesha-3.3-1.el7.x86_64 (centos-nfs-ganesha30) Requires: libntirpc.so.3.3()(64bit) Error: Package: nfs-ganesha-utils-3.3-1.el7.x86_64 (centos-nfs-ganesha30) Requires: libntirpc.so.3.3(NTIRPC_3.3)(64bit) Error: Package: nfs-ganesha-utils-3.3-1.el7.x86_64 (centos-nfs-ganesha30) Requires: libntirpc.so.3.3()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest In fact I don't have libntirpc 3.3 in my system: (BETA) root@data2:~$ yum info libntirpc.x86_64 Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirrors.clouvider.net * centos-gluster7: mirrors.clouvider.net * centos-nfs-ganesha30: mirror.sov.uk.goscomb.net * epel: ftp.nluug.nl * extras: mirror.netweaver.uk * updates: mirror.sov.uk.goscomb.net Installed Packages Name : libntirpc Arch : x86_64 Version : 3.2 Release : 1.el7 Size : 285 k Repo : installed From repo : centos-nfs-ganesha30 [...] As you can see, I'm using the repo from centos-release-nfs-ganesha30-1.0-2.el7.centos.noarch, the latest one available for CentOS7. Am I doing something wrong or maybe the libntirpc isn't available at CentOS Storage SIG repo yet? Cheers, Alberto Bengoa

3 3

dbus-send AddExport is failing with "Error org.freedesktop.DBus.Error.InvalidArgs: Error finding exports: EXPORT(Export_Id=3, ...).FSAL(Name="VFS") because No such file or directory"
by roshandkolhe＠gmail.com 17 Jun '20

17 Jun '20

Hi, I am exploring dynamic export in NFS-Ganesha using dbus-send. I could compile NFS-Ganesha with "USE_DBUS=ON" and could also start the ganesha.nfsd. The exports which were present in my config file are properly up when I started ganesha.nfsd. But, I am not able to add any new export. dbus-send command is always failing with below error [root@localhost ~]# ls -lrt /home/ total 0 drwxr-xr-x. 3 root root 36 Jun 2 21:22 ganesha_nfs_v3 drwxr-xr-x. 2 root root 6 Jun 10 18:18 ganesha_1 drwxr-xr-x. 8 root root 199 Jun 11 15:00 ganesha_nfs_v4 [root@localhost ~]# sudo dbus-send --print-reply --system --dest=org.ganesha.nfsd /org/ganesha/nfsd/ExportMgr org.ganesha.nfsd.exportmgr.AddExport string:/etc/ganesha/export.conf 'string:EXPORT(Export_Id=3, Path="/home/ganesha_1/", Pseudo="/home/ganesha_1/", Transports="TCP").FSAL(Name="VFS")' Error org.freedesktop.DBus.Error.InvalidArgs: Error finding exports: EXPORT(Export_Id=3, Path="/home/ganesha_1/", Pseudo="/home/ganesha_1/", Transports="TCP").FSAL(Name="VFS") because No such file or directory [root@localhost ~]# Messages in "/var/log/ganesha.log": 11/06/2020 23:44:23 : epoch 5ee2736e : localhost.localdomain : ganesha.nfsd-26823[dbus_heartbeat] gsh_export_addexport :EXPORT :CRIT :Error finding exports: EXPORT(Export_Id=3, Path="/home/ganesha_1/", Pseudo="/home/ganesha_1/", Transports="TCP").FSAL(Name="VFS") because No such file or directory 11/06/2020 23:44:23 : epoch 5ee2736e : localhost.localdomain : ganesha.nfsd-26823[dbus_heartbeat] dbus_message_entrypoint :DBUS :MAJ :Method (AddExport) on (org.ganesha.nfsd.exportmgr) failed: name = (org.freedesktop.DBus.Error.InvalidArgs), message = (Error finding exports: EXPORT(Export_Id=3, Path="/home/ganesha_1/", Pseudo="/home/ganesha_1/", Transports="TCP").FSAL(Name="VFS") because No such file or directory) 11/06/2020 23:46:06 : epoch 5ee2736e : localhost.localdomain : ganesha.nfsd-26823[dbus_heartbeat] nfs_health :DBUS :WARN :Health status is unhealthy. enq new: 5445, old: 5441; deq new: 5441, old: 5441 Can someone please help on this? I have followed the steps mentioned in: https://github.com/nfs-ganesha/nfs-ganesha/wiki/Dbusinterface [root@localhost ~]# ps -ef | grep nfs root 26823 1 0 23:39 ? 00:00:00 /root/build_dir_v3_stable/ganesha.nfsd -f /etc/ganesha/ganesha.conf root 26854 25589 0 23:39 pts/1 00:00:00 grep --color=auto nfs [root@localhost ~]# cat /var/log/ganesha.log | grep dbus 11/06/2020 23:39:50 : epoch 5ee2736e : localhost.localdomain : ganesha.nfsd-26823[main] nfs_Start_threads :THREAD :EVENT :gsh_dbusthread was started successfully [root@localhost ~]# showmount -e Export list for localhost.localdomain: /home/ganesha_nfs_v3 (everyone) /home/ganesha_nfs_v4 (everyone) [root@localhost ~]# [root@localhost ~]# cat /etc/ganesha/ganesha.conf ## These are core parameters that affect Ganesha as a whole. NFS_CORE_PARAM { ## Configure the protocols that Ganesha will listen for. This is a hard ## limit, as this list determines which sockets are opened. This list ## can be restricted per export, but cannot be expanded. Protocols = 3, 4; # Enable NLM (network lock manager protocol) Enable_NLM = false; # lockmgr port NLM_PORT = 45075; Enable_RQUOTA = false; } ## These are defaults for exports. They can be overridden per-export. EXPORT_DEFAULTS { ## Restrict the protocols that may use this export. This cannot allow ## access that is denied in NFS_CORE_PARAM. Protocols = 3, 4; ## Access type for clients. Default is None, so some access must be ## given either here or in the export itself. Access_Type = RW; ## Whether to squash various users. Squash = No_Root_Squash; ## Allowed security types for this export Sectype = sys,krb5,krb5i,krb5p; } ## Configure settings for the object handle cache MDCACHE { ## The point at which object cache entries will start being reused. Entries_HWMark = 100000; } ## Configure logging. Default is to log to Syslog. Basic logging can also be ## configured from the command line LOG { ## Default log level for all components Default_Log_Level = EVENT; #Default_Log_Level = DEBUG; ## Configure per-component log levels. Components { FSAL = INFO; NFS4 = EVENT; NFS3 = EVENT; } ## Where to log Facility { name = FILE; destination = "/var/log/ganesha.log"; enable = active; } } NFS_KRB5 { Active_krb5 = false; } %include "/etc/ganesha/export.conf" [root@localhost ~]# cat /etc/ganesha/export.conf ## Configure an export for some file tree EXPORT { ## Export Id (mandatory, each EXPORT must have a unique Export_Id) Export_Id = 1; ## Exported path (mandatory) Path = /home/ganesha_nfs_v3/; ## Pseudo Path (required for NFSv4 or if mount_path_pseudo = true) Pseudo = /home/ganesha_nfs_v3/; Transports = "TCP"; ## Exporting FSAL FSAL { Name = VFS; } } EXPORT { ## Export Id (mandatory, each EXPORT must have a unique Export_Id) Export_Id = 2; ## Exported path (mandatory) Path = /home/ganesha_nfs_v4/; ## Pseudo Path (required for NFSv4 or if mount_path_pseudo = true) Pseudo = /home/ganesha_nfs_v4/; Transports = "TCP"; ## Exporting FSAL FSAL { Name = VFS; } } Just as a data point, DisplayExport and ShowExports are running fine. [root@localhost ~]# dbus-send --print-reply --system --dest=org.ganesha.nfsd /org/ganesha/nfsd/ExportMgr org.ganesha.nfsd.exportmgr.DisplayExport uint16:1 method return time=1591899610.781101 sender=:1.175 -> destination=:1.178 serial=623 reply_serial=2 uint16 1 string "/home/ganesha_nfs_v3" string "/home/ganesha_nfs_v3" string "" array [ ] [root@localhost ~]# dbus-send --print-reply --system --dest=org.ganesha.nfsd /org/ganesha/nfsd/ExportMgr org.ganesha.nfsd.exportmgr.ShowExports method return time=1591899620.339869 sender=:1.175 -> destination=:1.179 serial=633 reply_serial=2 struct { uint64 1591898990 uint64 170367428 } array [ struct { uint16 1 string "/home/ganesha_nfs_v3" boolean true boolean false boolean false boolean false boolean false boolean false boolean false boolean false struct { uint64 1591899616 uint64 118026535 } } struct { uint16 2 string "/home/ganesha_nfs_v4" boolean false boolean false boolean false boolean false boolean false boolean true boolean false boolean false struct { uint64 1591899006 uint64 449489142 } } struct { uint16 0 string "/" boolean false boolean false boolean false boolean false boolean false boolean false boolean false boolean false struct { uint64 1591898990 uint64 143657141 } } ] [root@localhost ~]#

7 8

Bug: useless logs/tries keyring.
by Marc Roos 15 Jun '20

15 Jun '20

If you specify the userid and access key in the conf, why look for keyring? And why log it a thousand times? nfs-ganesha-2.8.1.2-0.1.el7.x86_64 nfs-ganesha-ceph-2.8.1.2-0.1.el7.x86_64 Jun 14 14:28:05 xxx nfs-ganesha[481476]: 2020-06-14 14:28:05.277 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:05 xxx nfs-ganesha[481476]: 2020-06-14 14:28:05.278 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:05 xxx nfs-ganesha[481476]: 2020-06-14 14:28:05.278 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:05 xxx nfs-ganesha[481476]: 2020-06-14 14:28:05.324 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:05 xxx nfs-ganesha[481476]: 2020-06-14 14:28:05.325 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:05 xxx nfs-ganesha[481476]: 2020-06-14 14:28:05.325 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:06 xxx nfs-ganesha[481476]: 2020-06-14 14:28:06.282 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:06 xxx nfs-ganesha[481476]: 2020-06-14 14:28:06.283 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:06 xxx nfs-ganesha[481476]: 2020-06-14 14:28:06.283 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:06 xxx nfs-ganesha[481476]: 2020-06-14 14:28:06.290 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:06 xxx nfs-ganesha[481476]: 2020-06-14 14:28:06.291 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:06 xxx nfs-ganesha[481476]: 2020-06-14 14:28:06.291 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:07 xxx nfs-ganesha[481476]: 2020-06-14 14:28:07.356 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:07 xxx nfs-ganesha[481476]: 2020-06-14 14:28:07.358 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:07 xxx nfs-ganesha[481476]: 2020-06-14 14:28:07.358 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:07 xxx nfs-ganesha[481476]: 2020-06-14 14:28:07.364 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:07 xxx nfs-ganesha[481476]: 2020-06-14 14:28:07.365 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:07 xxx nfs-ganesha[481476]: 2020-06-14 14:28:07.365 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:08 xxx nfs-ganesha[481476]: 2020-06-14 14:28:08.426 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:08 xxx nfs-ganesha[481476]: 2020-06-14 14:28:08.428 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:08 xxx nfs-ganesha[481476]: 2020-06-14 14:28:08.428 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:08 xxx nfs-ganesha[481476]: 2020-06-14 14:28:08.434 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:08 xxx nfs-ganesha[481476]: 2020-06-14 14:28:08.435 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:08 xxx nfs-ganesha[481476]: 2020-06-14 14:28:08.435 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:09 xxx nfs-ganesha[481476]: 2020-06-14 14:28:09.497 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:09 xxx nfs-ganesha[481476]: 2020-06-14 14:28:09.499 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:09 xxx nfs-ganesha[481476]: 2020-06-14 14:28:09.499 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:09 xxx nfs-ganesha[481476]: 2020-06-14 14:28:09.516 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:09 xxx nfs-ganesha[481476]: 2020-06-14 14:28:09.517 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:09 xxx nfs-ganesha[481476]: 2020-06-14 14:28:09.517 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:10 xxx nfs-ganesha[481476]: 2020-06-14 14:28:10.729 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:10 xxx nfs-ganesha[481476]: 2020-06-14 14:28:10.731 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:10 xxx nfs-ganesha[481476]: 2020-06-14 14:28:10.731 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:10 xxx nfs-ganesha[481476]: 2020-06-14 14:28:10.738 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:10 xxx nfs-ganesha[481476]: 2020-06-14 14:28:10.739 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory Jun 14 14:28:10 xxx nfs-ganesha[481476]: 2020-06-14 14:28:10.739 7fed73a7aac0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.cephfs.xxxx.keyring,/etc/ceph/ceph.keyring,/etc/ce ph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory

2 1

NFS Ganesha on Ceph-RGW without Keyring
by bl＠brunol.com 11 Jun '20

11 Jun '20

Hello, We want the nfs-ganesha functionality to export an RGW Bucket to NFS, but without the need to know the keyring in ceph.conf. Is that possible? Thanks Bruno

2 1

Help with id_cache_size
by David Hansen 09 Jun '20

09 Jun '20

Hello Ganesha support. I have a customer running into some nasty intermittent connection issues an internal directory service (VAS) which ganesha is using to query group ownership of directories thanks to Manage_Gids = True; As such, we've been asked to inspect the caching mechanism of ganesha U/GID mapping and determined that the ID map cache size is 1009 entries, as set here: https://github.com/nfs-ganesha/nfs-ganesha/blob/d51394b49b644b69bec1c219c65… src/idmapper/idmapper_cache.c:76 #define id_cache_size 1009 Since the customer has 6000+ groups, they have expressed interest in increasing this value to 20011 (must be prime) to account for nested groups and such. Can you please confirm whether we would have to define this value ourselves and recompile ganesha, or whether it is configurable with a config file somehow? Thanks! -- *David Hansen * Support Engineer WekaIO, Inc. | Radically Simple Storage™ Support Line: +1 (855) 969-4030 M: +1-408-332-4550 W: www.weka.io

3 2

Ganesha / libntirpc 3.3
by Daniel Gryniewicz 08 Jun '20

08 Jun '20

We're happy to announce Ganesha and libntirpc versions 3.3. These are bug-fix updates to the stable V3 branches of the code. There are many bug fixes, and it's highly recommended that users update to these versions if possible. Daniel

1 0

ganesha_stats iov3 total,latency counters
by joe lin 07 Jun '20

07 Jun '20

Hi, Was going thru the ganesha_stats documentation and was not able to figure out what 'total' and 'latency' represent. what does 'total' represent in ganesha_stats iov3? what does 'latency' represent? How would I calculate the average latency? Thanks!

1 0

Ganesha 3.2 connection issue
by Becker, Jeffrey C. (ARC-TN)[InuTeq, LLC] 01 Jun '20

01 Jun '20

Hi. I just built ganesha 3.2, and am trying to set up a PROXY mount. I’m trying to resolve the following error. My server NFSD is up, running, and rpcinfo -p shows the right ports etc. nfs-ganesha-64067[pxy_rcv_thread] pxy_rpc_recv :FSAL :CRIT :Cannot connect to server 10.151.27.27:2049:2049 My ganesh.conf file is as follows. Please advise on how to proceed. Thanks. -Jeff ## These are core parameters that affect Ganesha as a whole. NFS_CORE_PARAM { ## Allow NFSv3 to mount paths with the Pseudo path, the same as NFSv4, ## instead of using the physical paths. mount_path_pseudo = true; ## Configure the protocols that Ganesha will listen for. This is a hard ## limit, as this list determines which sockets are opened. This list ## can be restricted per export, but cannot be expanded. Protocols = 4; } ## Configure NFSv4 NFSv4 { Alow_Numeric_Owners = true; Only_Numeric_Owners = true; } ## These are defaults for exports. They can be overridden per-export. EXPORT_DEFAULTS { ## Access type for clients. Default is None, so some access must be ## given either here or in the export itself. Access_Type = RW; } ## Configure settings for the object handle cache CACHEINODE { ## The point at which object cache entries will start being reused. Entries_HWMark = 100000; } ## Configure exports EXPORT { ## Export Id (mandatory, each EXPORT must have a unique Export_Id) Export_Id = 1111; ## Exported path (mandatory) Path = /nobackupp16/jcbecker; ## Pseudo Path (required for NFSv4 or if mount_path_pseudo = true) Pseudo = /foo; ## Restrict the protocols that may use this export. This cannot allow ## access that is denied in NFS_CORE_PARAM. #Protocols = 3,4; ## Access type for clients. Default is None, so some access must be ## given. It can be here, in the EXPORT_DEFAULTS, or in a CLIENT block Access_Type = RW; ## Whether to squash various users. Squash = root_squash; ## Allowed security types for this export #Sectype = sys,krb5,krb5i,krb5p; ## Exporting FSAL FSAL { Name = PROXY; Srv_Addr = 10.151.27.27; } CLIENT { Clients = 10.151.26.24; } } ## Configure logging. Default is to log to Syslog. Basic logging can also be ## configured from the command line LOG { ## Default log level for all components Default_Log_Level = INFO; ## Configure per-component log levels. Components { FSAL = INFO; NFS4 = EVENT; } ## Where to log Facility { name = FILE; destination = "/mnt/nbnfs2/jcbecker/reexporter/var/log/ganesha.log"; enable = active; } }

2 1