Malahal Naineni
2015-Jun-17 17:51 UTC
[Gluster-users] [Nfs-ganesha-devel] Problems in /usr/libexec/ganesha/dbus-send.sh and ganesha dbus interface when disabling exports from gluster
Alessandro De Salvo [Alessandro.DeSalvo at roma1.infn.it] wrote:> What?s more worrying is the problem with the dbus. Issuing a DisplayExport before the RemoveExport apparently fixes the problem, so something like this always works: > > # dbus-send --print-reply --system --dest=org.ganesha.nfsd /org/ganesha/nfsd/ExportMgr org.ganesha.nfsd.exportmgr.DisplayExport uint16:2 > # dbus-send --print-reply --system --dest=org.ganesha.nfsd /org/ganesha/nfsd/ExportMgr org.ganesha.nfsd.exportmgr.RemoveExport uint16:2 > > So, it?s like the DisplayExport is forcing someway a refresh that is needed by the RemoveExport. Any idea why? > I?m using the latest version of ganesha 2.2.0, i.e. 2.2.0-3.I used the same exact command above (the second one that removes an export) after restarting ganesha, and it just worked fine. I use GPFS FSAL (neither gluster nor VFS). Not sure why you need to use DisplayExport before using RemoveExport. Try to trace 'DBUS' component at FULL_DEBUG (or maybe everything at FULL_DEBUG) and post the log. The error you reported means we are NOT responding to the dbus message which is very odd! Reagrds, Malahal.
Alessandro De Salvo
2015-Jun-17 18:06 UTC
[Gluster-users] [Nfs-ganesha-devel] Problems in /usr/libexec/ganesha/dbus-send.sh and ganesha dbus interface when disabling exports from gluster
Hi Malahal,> Il giorno 17/giu/2015, alle ore 19:51, Malahal Naineni <malahal at us.ibm.com> ha scritto: > > Alessandro De Salvo [Alessandro.DeSalvo at roma1.infn.it] wrote: >> What?s more worrying is the problem with the dbus. Issuing a DisplayExport before the RemoveExport apparently fixes the problem, so something like this always works: >> >> # dbus-send --print-reply --system --dest=org.ganesha.nfsd /org/ganesha/nfsd/ExportMgr org.ganesha.nfsd.exportmgr.DisplayExport uint16:2 >> # dbus-send --print-reply --system --dest=org.ganesha.nfsd /org/ganesha/nfsd/ExportMgr org.ganesha.nfsd.exportmgr.RemoveExport uint16:2 >> >> So, it?s like the DisplayExport is forcing someway a refresh that is needed by the RemoveExport. Any idea why? >> I?m using the latest version of ganesha 2.2.0, i.e. 2.2.0-3. > > I used the same exact command above (the second one that removes an > export) after restarting ganesha, and it just worked fine. I use GPFS > FSAL (neither gluster nor VFS). > > Not sure why you need to use DisplayExport before using RemoveExport. > Try to trace 'DBUS' component at FULL_DEBUG (or maybe everything at > FULL_DEBUG) and post the log. The error you reported means we are NOT > responding to the dbus message which is very odd!Indeed! This is why I was worried :-) I?m attaching the ganesha.log with NIV_FULL_DEBUG, you can see the restart at the end, due to my attempt of RemoveExport, which always gave me the same error as before. Thanks, Alessandro -------------- next part -------------- A non-text attachment was scrubbed... Name: ganesha-20150617.log.gz Type: application/x-gzip Size: 23346 bytes Desc: not available URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150617/12512880/attachment.gz> -------------- next part --------------> > Reagrds, Malahal. > >-------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 1770 bytes Desc: not available URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150617/12512880/attachment.p7s>