Bug 1114976

Summary:	nfs-ganesha: logs inside the /tmp directory
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Saurabh <saujain>
Component:	nfs-ganesha	Assignee:	Meghana <mmadhusu>
Status:	CLOSED ERRATA	QA Contact:	Saurabh <saujain>
Severity:	high	Docs Contact:
Priority:	high
Version:	rhgs-3.0	CC:	annair, mmadhusu, mzywusko, ndevos, nlevinki, nsathyan, skoduri, vagarwal
Target Milestone:	---
Target Release:	RHGS 3.1.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.1-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1116723 (view as bug list)		Environment:
Last Closed:	2015-07-29 04:33:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1116723, 1202842

Description Saurabh 2014-07-01 11:23:07 UTC

Description of problem:
Once the nfs-ganesha server is started it points to having logs in /tmp directory. So we need to overcome this problem, as /tmp should not be a default directory for having logs.

Version-Release number of selected component (if applicable):
nfs-ganesha-2.1.0.2-4.el6rhs.x86_64

How reproducible:
always

Steps to Reproduce:
1. create a volume, start it.
2. stop glusterfs-nfs
3. start nfs-ganesha server

Actual results:
[root@nfs1 ~]# ps -eaf | grep nfs
root     12767     1  2 Jun30 ?        00:30:50 /usr/bin/ganesha.nfsd -f /var/lib/glusterfs-ganesha/nfs-ganesha.conf -L /tmp/ganesha.log -N NIV_EVENT -d


Expected results:

default logs should not be in the directory "/tmp"

Additional info:

Comment 2 Meghana 2015-04-21 07:01:18 UTC

This issue has been fixed. And the present release overrides this behaviour.

Comment 6 Saurabh 2015-07-05 11:13:41 UTC

Now we have logs under the /var/log/ dir,

[root@nfs16 ~]# ls /var/log/ganesha*
/var/log/ganesha-gfapi.log  /var/log/ganesha.log

Comment 8 errata-xmlrpc 2015-07-29 04:33:04 UTC

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/RHSA-2015-1495.html