Bug 1116789 - coredump files getting collected in "/" not in /var/log/core
Summary: coredump files getting collected in "/" not in /var/log/core
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: distribution
Version: rhgs-3.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: RHGS 3.0.0
Assignee: Bala.FA
QA Contact: Saurabh
URL:
Whiteboard:
Depends On: 1123328
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-07 10:18 UTC by Saurabh
Modified: 2018-08-06 12:13 UTC (History)
11 users (show)

Fixed In Version: redhat-storage-server-3.0.0.3-2.el6rhs
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-22 19:43:57 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:1278 0 normal SHIPPED_LIVE Red Hat Storage Server 3.0 bug fix and enhancement update 2014-09-22 23:26:55 UTC

Description Saurabh 2014-07-07 10:18:35 UTC
Description of problem:
This problem is about getting the coredump files getting collected in "/" for the crash i.e. seen for gluster issues, whereas the correct behaviour is about getting them collected in "/var/run/gluster" 

Version-Release number of selected component (if applicable):
glusterfs-3.6.0.24-1.el6rhs.x86_64

How reproducible:
always on this build, not earlier ones

Expected results:
cores in /var/run/gluster

Additional info:

Comment 2 Bala.FA 2014-07-16 03:21:21 UTC
Default core location in RHS is /var/log/cores not /var/run/gluster

Comment 3 Bala.FA 2014-07-16 03:23:09 UTC
(In reply to Bala.FA from comment #2)
> Default core location in RHS is /var/log/cores not /var/run/gluster

Its /var/log/core.

Comment 4 Bala.FA 2014-07-16 03:35:27 UTC
Patch is under review at https://code.engineering.redhat.com/gerrit/29206

Comment 6 Saurabh 2014-09-01 06:43:49 UTC
Moving this BZ to ASSIGNED, as even now the core is found in "/" path only

[root@nfs2 ~]# kill -11 13382
[root@nfs2 ~]# ls /core.133*
/core.13382
[root@nfs2 ~]# 
[root@nfs2 ~]# 
[root@nfs2 ~]# rpm -qa | grep redhat
redhat-storage-logos-60.0.17-1.el6rhs.noarch
redhat-indexhtml-6-6.el6.noarch
redhat-release-server-6Server-6.5.0.1.el6.x86_64
redhat-storage-server-3.0.0.3-2.el6rhs.noarch

Comment 7 Bala.FA 2014-09-01 23:11:06 UTC
How did you get the system to redhat-storage-server-3.0.0.3-2.el6rhs.noarch?

No intermediate QA released are not supported though.

Comment 8 Bala.FA 2014-09-01 23:11:59 UTC
(In reply to Bala.FA from comment #7)
> How did you get the system to redhat-storage-server-3.0.0.3-2.el6rhs.noarch?
> 
> No intermediate QA released are not supported though.

In terms of upgrade.

Comment 9 Saurabh 2014-09-02 02:08:36 UTC
Yum update the package, that's how I did it.

Comment 11 Saurabh 2014-09-02 11:40:40 UTC
with fresh install of the latest iso available, I was able to verify the BZ.

[root@rhsauto032 ~]# rpm -qa | grep redhat
redhat-storage-server-3.0.0.3-2.el6rhs.noarch
beakerlib-redhat-1-13.el6eso.noarch
redhat-storage-logos-60.0.17-1.el6rhs.noarch
redhat-indexhtml-6-6.el6.noarch
redhat-release-server-6Server-6.5.0.1.el6.x86_64
[root@rhsauto032 ~]# 
[root@rhsauto032 ~]# 
[root@rhsauto032 ~]# 
[root@rhsauto032 ~]# 
[root@rhsauto032 ~]# 
[root@rhsauto032 ~]# kill -11 3794
[root@rhsauto032 ~]# ls /
bin  boot  cgroup  data  dev  etc  home  lib  lib64  lost+found  media  mnt  opt  proc  rhev  rhs  root  sbin  selinux  srv  sys  tmp  usr  var
[root@rhsauto032 ~]# ls /var/log/core/
core.3794.1409614155.dump
[root@rhsauto032 ~]# ls -l /var/log/core/
total 30296
-rw------- 1 root root 106332160 Sep  2 04:59 core.3794.1409614155.dump

Comment 13 errata-xmlrpc 2014-09-22 19:43:57 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.

http://rhn.redhat.com/errata/RHEA-2014-1278.html


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