Hi, In your ganesha-ha.conf do you have your virtual ip adresses set something like this : VIP_tlxdmz-nfs1="192.168.22.33" VIP_tlxdmz-nfs2="192.168.22.34" Renaud De : gluster-users-bounces@xxxxxxxxxxx [mailto:gluster-users-bounces@xxxxxxxxxxx] De la part de Hetz Ben Hamo Envoyé : 20 décembre 2017 04:35 À : gluster-users@xxxxxxxxxxx Objet : glusterfs, ganesh, and pcs rules Hi, I've just created again the gluster with NFS ganesha. Glusterfs version 3.8 When I run the command gluster nfs-ganesha enable - it returns a success. However, looking at the pcs status, I see this: [root@tlxdmz-nfs1 ~]# pcs status Cluster name: ganesha-nfs Stack: corosync Current DC: tlxdmz-nfs2 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum Last updated: Wed Dec 20 09:20:44 2017 Last change: Wed Dec 20 09:19:27 2017 by root via cibadmin on tlxdmz-nfs1 2 nodes configured 8 resources configured Online: [ tlxdmz-nfs1 tlxdmz-nfs2 ] Full list of resources: Clone Set: nfs_setup-clone [nfs_setup] Started: [ tlxdmz-nfs1 tlxdmz-nfs2 ] Clone Set: nfs-mon-clone [nfs-mon] Started: [ tlxdmz-nfs1 tlxdmz-nfs2 ] Clone Set: nfs-grace-clone [nfs-grace] Started: [ tlxdmz-nfs1 tlxdmz-nfs2 ] tlxdmz-nfs1-cluster_ip-1 (ocf::heartbeat:IPaddr): Stopped tlxdmz-nfs2-cluster_ip-1 (ocf::heartbeat:IPaddr): Stopped Failed Actions: * tlxdmz-nfs1-cluster_ip-1_monitor_0 on tlxdmz-nfs2 'not configured' (6): call=23, status=complete, exitreason='IP address (the ip parameter) is mandatory', last-rc-change='Wed Dec 20 09:19:28 2017', queued=0ms, exec=26ms * tlxdmz-nfs2-cluster_ip-1_monitor_0 on tlxdmz-nfs2 'not configured' (6): call=27, status=complete, exitreason='IP address (the ip parameter) is mandatory', last-rc-change='Wed Dec 20 09:19:28 2017', queued=0ms, exec=26ms * tlxdmz-nfs1-cluster_ip-1_monitor_0 on tlxdmz-nfs1 'not configured' (6): call=23, status=complete, exitreason='IP address (the ip parameter) is mandatory', last-rc-change='Wed Dec 20 09:19:28 2017', queued=0ms, exec=24ms * tlxdmz-nfs2-cluster_ip-1_monitor_0 on tlxdmz-nfs1 'not configured' (6): call=27, status=complete, exitreason='IP address (the ip parameter) is mandatory', last-rc-change='Wed Dec 20 09:19:28 2017', queued=0ms, exec=61ms Daemon Status: corosync: active/disabled pacemaker: active/disabled pcsd: active/enabled Any suggestion how this can be fixed when enabling nfs-ganesha when invoking the above command or anything else that I can do to fixed the failed actions? Thanks _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-users
