Description of problem: Update the export file of volume, execute refresh-config as this command helps to update the export file of volume on all nodes and update the nfs-ganesha process on all nodes. Version-Release number of selected component (if applicable): glusterfs-3.7.1-8.el6rhs.x86_64 nfs-ganesha-2.2.0-4.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1. export a volume using the ganesha.enable 2. change export file of the volume for setting root_squash on 3. execute refresh-config from same node Actual results: [root@nfs11 ~]# time bash /usr/libexec/ganesha/ganesha-ha.sh --refresh-config /etc/ganesha/ vol3 export.vol3.conf 100% 503 0.5KB/s 00:00 method return sender=:1.61 -> dest=:1.65 reply_serial=2 export.vol3.conf 100% 503 0.5KB/s 00:00 method return sender=:1.62 -> dest=:1.66 reply_serial=2 export.vol3.conf 100% 503 0.5KB/s 00:00 method return sender=:1.62 -> dest=:1.66 reply_serial=2 method return sender=:1.71 -> dest=:1.75 reply_serial=2 Expected results: dbus messages should not seen on stdout or they should be made more meaningful Additional info:
Doc text is edited. Please sign off to be included in Known Issues.
Included the edited text as known issue.
Presently refresh config fails, time /usr/libexec/ganesha/ganesha-ha.sh --refresh-config /etc/ganesha/ testvol Error: refresh-config failed on nfs12. just for fyi, the passwordless connections are in place, i = [nfs11 nfs12 nfs13 nfs15] ssh -i /var/lib/glusterd/nfs/secret.pem $i "hostname" nfs11 nfs11 ------------ nfs12 nfs12 ------------ nfs13 nfs13 ------------ nfs15 nfs15 ------------
Please provide the error messages logged (/var/log/messages, /var/log/ganesha.log, /var/log/ganesha-gfapi.log) when this issue is seen.
Created attachment 1086455 [details] nfs12 ganesha.log
Created attachment 1086456 [details] nfs12 ganesha-gfapi.log
Created attachment 1086457 [details] nfs12 messages
Created attachment 1086458 [details] nfs11 ganesha.log
Created attachment 1086460 [details] nfs11 messages
Created attachment 1086462 [details] nfs11 ganesha-gfapi.log
On nfs12- 26/10/2015 16:56:37 : epoch 562e0dec : nfs12 : ganesha.nfsd-27481[main] nfs_Start_threads :THREAD :EVENT :reaper thread was started successfully 26/10/2015 16:56:37 : epoch 562e0dec : nfs12 : ganesha.nfsd-27481[reaper] nfs_in_grace :STATE :EVENT :NFS Server Now IN GRACE 26/10/2015 16:56:37 : epoch 562e0dec : nfs12 : ganesha.nfsd-27481[main] nfs_Start_threads :THREAD :EVENT :General fridge was started successfully 26/10/2015 16:56:37 : epoch 562e0dec : nfs12 : ganesha.nfsd-27481[main] nfs_start :NFS STARTUP :EVENT :------------------------------------------------- 26/10/2015 16:56:37 : epoch 562e0dec : nfs12 : ganesha.nfsd-27481[main] nfs_start :NFS STARTUP :EVENT : NFS SERVER INITIALIZED 26/10/2015 16:56:37 : epoch 562e0dec : nfs12 : ganesha.nfsd-27481[main] nfs_start :NFS STARTUP :EVENT :------------------------------------------------- 26/10/2015 16:57:37 : epoch 562e0dec : nfs12 : ganesha.nfsd-27481[reaper] nfs_in_grace :STATE :EVENT :NFS Server Now NOT IN GRACE 26/10/2015 17:02:43 : epoch 562e0dec : nfs12 : ganesha.nfsd-27481[dbus_heartbeat] glusterfs_create_export :FSAL :EVENT :Volume testvol exported at : '/' 26/10/2015 17:37:32 : epoch 562e0dec : nfs12 : ganesha.nfsd-27481[dbus_heartbeat] dbus_message_entrypoint :DBUS :MAJ :Method (RemoveExport) on (org.ganesha.nfsd.exportmgr) failed: name = (org.freedesktop.DBus.Error.InvalidArgs), message = (lookup_export failed with Export id not found) 26/10/2015 17:37:43 : epoch 562e0dec : nfs12 : ganesha.nfsd-27481[dbus_heartbeat] glusterfs_create_export :FSAL :EVENT :Volume testvol exported at : ' Looks like volume testvol is exported with a different ExportID on nfs12. May be a configuration issue. Request QE to reproduce/provide setup to debug further.
Got the setup from QE. There is an issue with output parsing in ganesha-ha.sh script. Posted the fix upstream for review - http://review.gluster.org/#/c/12439/
included in the 3.1.2 rebase
I think it has failed QA test with the latest 3.1.2 rebase code. Saurabh, could you please confirm?
As per result, # time bash /usr/libexec/ganesha/ganesha-ha.sh --refresh-config /etc/ganesha/ vol0 Refresh-config completed on vm2. Refresh-config completed on vm3. Refresh-config completed on vm4. Success: refresh-config completed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0193.html