On 10/03/2017 02:15 AM, Bernhard Dübi wrote:
Hi Soumya,
what I can say so far:
it is working on a standalone system but not on the clustered system
Hi,
Sorry for the delay. Locking seem to have failed due to below
nsm_monitor error :
03/10/2017 14:27:38 : epoch 59cbce8c : chvirnfsprd12 :
ganesha.nfsd-8516[work-2] nsm_monitor :NLM :DEBUG :Monitor
chglboraprd10.fpprod.corp
03/10/2017 14:27:38 : epoch 59cbce8c : chvirnfsprd12 :
ganesha.nfsd-8516[work-2] nsm_monitor :NLM :CRIT :Can not monitor
chglboraprd10.fpprod.corp SM_MON status 1
03/10/2017 14:27:38 : epoch 59cbce8c : chvirnfsprd12 :
ganesha.nfsd-8516[work-2] nlm4_Lock :NLM :DEBUG :REQUEST RESULT:
nlm4_Lock NLM4_DENIED_NOLOCKS
And you have mentioned that it happens only on clustered system. Could
you please check following
-- Ensure that client and server hostnames are dns resolvable
-- Is rpc.statd service running?
#ps uax | grep statd
# rpcinfo -p | grep status
If not running please start the below service -
# systemctl start rpc-statd.service
Now restart nfs-ganesha service as well. If it still doesn't work,
-- please check if there are any errors in system logs
(/var/log/messages) wrt statd service
-- verify if the below folders are present
#ls -ld /var/lib/nfs
(this path should be symlink to the gluster_storage mount point -
/var/run/gluster/shared_storage/nfs_ganesha)
#ls /var/lib/nfs/statd/
sm sm.bak state
Thanks,
Soumya
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users
