Bug 1228153
| Summary: | nfs-ganesha: Fix gfapi.log location | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Soumya Koduri <skoduri> |
| Component: | nfs-ganesha | Assignee: | Meghana <mmadhusu> |
| Status: | CLOSED ERRATA | QA Contact: | storage-qa-internal <storage-qa-internal> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | rhgs-3.1 | CC: | asrivast, bmohanra, mmadhusu, ndevos, nlevinki, rcyriac, saujain, skoduri, vagarwal |
| Target Milestone: | --- | Flags: | mmadhusu:
needinfo+
|
| Target Release: | RHGS 3.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | nfs-ganesha-2.2.0-2 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the logs from FSAL_GLUSTER/gfapi were saved in the "/tmp" directory. Due to this, the logs would get lost when /tmp gets cleared. With this fix, nfs-ganesha will now log to /var/log/ganesha-gfapi.log and troubleshooting is much easier due to the availability of a longer history.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-07-29 04:56:31 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: | 1202842 | ||
|
Description
Soumya Koduri
2015-06-04 10:14:33 UTC
request you to put the gerrit url that fixes the issue. https://review.gerrithub.io/#/c/233254/ fixes the issue. [root@nfs11 ~]# rpm -qa | grep ganesha glusterfs-ganesha-3.7.1-3.el6rhs.x86_64 nfs-ganesha-2.2.0-3.el6rhs.x86_64 nfs-ganesha-gluster-2.2.0-3.el6rhs.x86_64 [root@nfs11 ~]# [root@nfs11 ~]# [root@nfs11 ~]# ls /var/log/ganesha-gfapi.log /var/log/ganesha-gfapi.log Hi Meghana, The doc text is updated. Please review the same and share your technical review comments. If it looks ok, then sign-off on the same. Regards, Bhavana 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 |