Bug 1464727
Summary: | glusterd: crash on parsing /proc/<pid>/cmdline after node restart after ungraceful shutdown | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Milind Changire <mchangir> |
Component: | glusterd | Assignee: | Mohit Agrawal <moagrawa> |
Status: | CLOSED ERRATA | QA Contact: | Bala Konda Reddy M <bmekala> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.3 | CC: | amukherj, mchangir, moagrawa, rcyriac, rhinduja, rhs-bugs, storage-qa-internal, vbellur |
Target Milestone: | --- | ||
Target Release: | RHGS 3.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | 3.3.0-devel-freeze-exception | ||
Fixed In Version: | glusterfs-3.8.4-32 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-09-21 05:02:13 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: | 1417151 |
Comment 2
Atin Mukherjee
2017-06-26 06:57:32 UTC
I think this can be addressed as part of https://review.gluster.org/#/c/17601/ Mohit - thoughts? (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 upstream patch : https://review.gluster.org/#/c/17601/ upstream patch : https://review.gluster.org/#/c/17601/ downstream patch : https://code.engineering.redhat.com/gerrit/#/c/110184/ 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. 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 |