Bug 1516699

Summary:	[Ganesha] : ganesha.log should be inside /var/log/ganesha.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Ambarish <asoman>
Component:	nfs-ganesha	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED ERRATA	QA Contact:	Manisha Saini <msaini>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.4	CC:	amukherj, bturner, chpai, dang, ffilz, jthottan, kkeithle, mbenjamin, rhinduja, rhs-bugs, skoduri, ssaha, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.4.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	nfs-ganesha-2.5.5-1	Doc Type:	Bug Fix
Doc Text:	With Red Hat Gluster Storage 3.4, NFS-Ganesha log files have been moved to the /var/log/ganesha subdirectory.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-04 06:53:36 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:	1503137

Description Ambarish 2017-11-23 09:54:44 UTC

Description of problem:
-----------------------

ganesha.log looks out of place inside /var/log.

Good to keep it inside /var/log/ganesha (just like ganesha-gfapi logs) for better usability and easy consumption.


Version-Release number of selected component (if applicable):
--------------------------------------------------------------

nfs-ganesha-gluster-2.5.4-1.el7rhgs.x86_64
glusterfs-ganesha-3.12.2-1.el7rhgs.x86_64


How reproducible:
-----------------

100%

Comment 2 Daniel Gryniewicz 2017-11-27 16:45:08 UTC

This is already the default upstream and on 2.5.  It was done by commit 58877b02576334e9f9b21b2dec881031db7db49c in April.

Comment 5 Ambarish 2018-03-01 08:52:21 UTC

Both logs inside /var/log/ganesha in 2.5.5-2 , Verified.

Comment 10 errata-xmlrpc 2018-09-04 06:53:36 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://access.redhat.com/errata/RHEA-2018:2610