Bug 1464727 - glusterd: crash on parsing /proc/<pid>/cmdline after node restart after ungraceful shutdown
Summary: glusterd: crash on parsing /proc/<pid>/cmdline after node restart after ungra...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.3.0
Assignee: Mohit Agrawal
QA Contact: Bala Konda Reddy M
URL:
Whiteboard: 3.3.0-devel-freeze-exception
Depends On:
Blocks: 1417151
TreeView+ depends on / blocked
 
Reported: 2017-06-25 05:58 UTC by Milind Changire
Modified: 2017-09-21 05:02 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.8.4-32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-21 05:02:13 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2774 0 normal SHIPPED_LIVE glusterfs bug fix and enhancement update 2017-09-21 08:16:29 UTC

Comment 2 Atin Mukherjee 2017-06-26 06:57:32 UTC 
Can you please attach the core along with 't a a bt' output?
Comment 3 Atin Mukherjee 2017-06-26 06:59:04 UTC 
I think this can be addressed as part of https://review.gluster.org/#/c/17601/

Mohit - thoughts?
Comment 4 Milind Changire 2017-06-26 07:24:39 UTC 
(In reply to Atin Mukherjee from comment #2)
> Can you please attach the core along with 't a a bt' output?

There was a backtrace in /var/log/glusterfs/glusterd.log, which I have printed using my print-backtrace.sh to get the line numbers resolved. There's no core file that got dumped.

The resolved backtrace is available at comment #0 under Additional Info
Comment 5 Atin Mukherjee 2017-06-27 04:02:41 UTC 
upstream patch : https://review.gluster.org/#/c/17601/
Comment 8 Atin Mukherjee 2017-06-27 14:04:26 UTC 
upstream patch : https://review.gluster.org/#/c/17601/
downstream patch : https://code.engineering.redhat.com/gerrit/#/c/110184/
Comment 10 Bala Konda Reddy M 2017-07-17 06:31:00 UTC 
BUILD: 3.8.4.32

Followed the steps mentioned by Milind, performed kill -9 on the brick process and glusterd and restarted glusterd on a node. No glusterd crash is seen. Hence marking it as verified.
Comment 12 errata-xmlrpc 2017-09-21 05:02:13 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/RHBA-2017:2774
Note You need to log in before you can comment on or make changes to this bug.