From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR; rv:1.2.1) Gecko/20030225 Description of problem: The Goal is making nfs service running on cluster (ES 3) 1. When creating NFS service with cluster-config (with nfs druid) i got this error message in /var/log/messages service error : StartStopNFS : Failed restarting nfs daemon : /usr/lib/clumanager/services/services : line 64 : Arr�t : Command not found service error : StartStopNFS : Failed restarting nfs daemon : /usr/lib/clumanager/services/services : line 65 : Demarrage : Command not found service error : can not stop NFS ... nb : I used French Keyboard, that mean Arr�t = stop, Demarrage = start 2. When creating NFS service with cluster-manager (not with druid, but like generic service ... "new service, add ip adress, add special device etc ...." result : when starting nfs service bye "clusvcadm -e nfs-service" on one node1, it's ok with clustat (i saw nfs-service started on node1, but clumanager did not really start nfsd daemon when i execute "ps -ef | grep -i nfs" nb : i use "None" in user script field (i did not use /etc/init.d/nfs) 3. the the same test than 2. but i used /etc/init.d/nfs result : when starting nfs service bye "clusvcadm -e nfs-service" on one node1, clustat tell me that nfs-service failed (node1) ... But when "ps -ef |grep -i nfs" i saw all nfsd daemon present .... !!!! Could you please tell me if it's really a bug ?? and give me informations that allow me to use NFS with clumanager .... thank you very much ... customer's waiting for our informations Can Version-Release number of selected component (if applicable): clumanager-1.2.3-1 and redhat-config-cluster-1.0.1-2 How reproducible: Always Steps to Reproduce: 1. creating NFS service with clumanager (cluster-config tool) 2. starting nfs service 3. clustat to see result Actual Results: nfs service can not be started and not available Expected Results: nfs service will be started by clumanager (clusvcadm -e nfs-service) Additional info: clumanager-1.2.3-1 and redhat-config-cluster-1.0.1-2 are used
Created attachment 96472 [details] see this joined file
To configure NFS services, you should have the NFS daemons always running on both members. The cluster manages the exports; it should not start & stop the NFS servers themselves. On all cluster members, run: # chkconfig --level 2345 nfs on # chkconfig --level 2345 nfslock on # service nfs start # service nfslock start For NFS services under Cluster Manager, you do not need to specify a user script.
That is to say: Unlike, for instance, Samba, the NFS daemons are in the kernel. They can not be bound to a specific IP address in the way Samba and other services can. Suppose you have a machine which serves both clustered and non-clustered NFS exports - stopping or restarting the NFS daemons inside of Cluster Manager would break all of your non-cluster exports, a very bad thing!
As it has been over 4 months since the last comment, I'm closing this.