Bug 1234780 - nfs-ganesha: grep: /ganesha-ha.conf: No such file or directory
Summary: nfs-ganesha: grep: /ganesha-ha.conf: No such file or directory
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: nfs-ganesha
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Kaleb KEITHLEY
QA Contact: Saurabh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-23 08:47 UTC by Saurabh
Modified: 2016-01-19 06:14 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-10 07:42:48 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1224610 0 high CLOSED nfs-ganesha: execution of script ganesha-ha.sh throws a error for a file 2021-02-22 00:41:40 UTC

Internal Links: 1224610

Description Saurabh 2015-06-23 08:47:49 UTC
Description of problem:

 While executing the status command for ganesha-ha.sh script it throws this error,
[root@nfs11 ~]# time /usr/libexec/ganesha/ganesha-ha.sh --status
grep: /ganesha-ha.conf: No such file or directory
grep: /ganesha-ha.conf: No such file or directory
grep: /ganesha-ha.conf: No such file or directory

Version-Release number of selected component (if applicable):
glusterfs-3.7.1-4.el6rhs.x86_64
nfs-ganesha-2.2.0-3.el6rhs.x86_64
How reproducible:
always


Expected results:
script should not throw any error.

Additional info:

Comment 3 Meghana 2015-07-13 06:38:12 UTC
Hi, 
Looks like this bug is fixed as port of the fix of this bug,
https://bugzilla.redhat.com/show_bug.cgi?id=1224610

Please check the behaviour in the recent build and update the bug.

Comment 4 Kaleb KEITHLEY 2015-07-20 12:05:19 UTC
This was fixed in commit f76bbb74e489bc9d34eee082f28ce71b606a3b5d

Comment 5 Saurabh 2015-07-21 08:16:00 UTC
[root@nfs1 ~]# time /usr/libexec/ganesha/ganesha-ha.sh --status
Cluster name: G1437076740.12
Last updated: Tue Jul 21 03:00:23 2015
Last change: Fri Jul 17 06:38:29 2015
Stack: corosync
Current DC: nfs4 (3) - partition with quorum
Version: 1.1.12-a14efad
4 Nodes configured
16 Resources configured


Online: [ nfs1 nfs2 nfs3 nfs4 ]

Full list of resources:

 Clone Set: nfs-mon-clone [nfs-mon]
     Started: [ nfs1 nfs2 nfs3 nfs4 ]
 Clone Set: nfs-grace-clone [nfs-grace]
     Started: [ nfs1 nfs2 nfs3 nfs4 ]
 nfs1-cluster_ip-1	(ocf::heartbeat:IPaddr):	Started nfs1 
 nfs1-trigger_ip-1	(ocf::heartbeat:Dummy):	Started nfs1 
 nfs2-cluster_ip-1	(ocf::heartbeat:IPaddr):	Started nfs2 
 nfs2-trigger_ip-1	(ocf::heartbeat:Dummy):	Started nfs2 
 nfs3-cluster_ip-1	(ocf::heartbeat:IPaddr):	Started nfs3 
 nfs3-trigger_ip-1	(ocf::heartbeat:Dummy):	Started nfs3 
 nfs4-cluster_ip-1	(ocf::heartbeat:IPaddr):	Started nfs4 
 nfs4-trigger_ip-1	(ocf::heartbeat:Dummy):	Started nfs4 

Failed actions:
    nfs-mon_monitor_10000 on nfs1 'unknown error' (1): call=69, status=Timed Out, exit-reason='none', last-rc-change='Mon Jul 20 08:33:51 2015', queued=0ms, exec=0ms


PCSD Status:
  nfs3: Online
  nfs2: Online
  nfs4: Online
  nfs1: Online

Daemon Status:
  corosync: active/disabled
  pacemaker: active/disabled
  pcsd: active/disabled


Note You need to log in before you can comment on or make changes to this bug.