Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionBhushan Ranpise
2019-04-12 14:37:35 UTC
Description of problem:
I have a case- 02358588, where the customer wants the gluster-related commands to be captured by the gluster sos plugin itself:
- gluster vol info
- gluster vol status
- gluster peer status
- gluster volume get <volname> all (for all volumes)
- gluster get-state
- "killall -USR1 glusterd" on the node where you see the problem and in one node without it to compare to see glusterd state info
- "for gpid in $(ps aux | grep "glusterfs " | grep :_ | awk '{print $2}') ; do kill -USR1 $gpid ; done" on node with hanging VM to collect glusterfs state info
- ps -Ll -p <pid of a zombie process>
- cat /proc/<pid of a zombie process>/task/*/stack
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Following up on #c5:
- new to add:
gluster volume get <volname> all (for all volumes)
gluster get-state
killall -USR1 glusterd (to be added to glusterfs/glusterfsd killall cmd, under dump option)
for gpid in $(ps aux | grep "glusterfs " | grep :_ | awk '{print $2}') ; do kill -USR1 $gpid ; done (also under dump option)
ps -Ll -p <pid of a zombie process>
cat /proc/<pid of a zombie process>/task/*/stack
I recall there were some concerns about /proc collection, but havent found anything specific to tasks/stack - this seem to me safe.
Question1: Shall we do so for *all* zombie processes, even unrelated to gluster? Or how to filter what zombie processes to get details for?
Question2: We can also enable the '-k gluster.dump=on' via some new RHHI preset in sosreport - just let me know how to determine the system belongs to RHHI (i.e. some specific package installed?).
> Question2: We can also enable the '-k gluster.dump=on' via some new RHHI
> preset in sosreport - just let me know how to determine the system belongs
> to RHHI (i.e. some specific package installed?).
A preset could work - from BZ1699401 we'll be adding a RHHI profile to sos-collector, so we can get it from both directions here.
RHHI requires the presence of _both_ the gluster and rhv packages. For the nodes that means the qemu-kvm-rhev package.
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-2020:1127
Description of problem: I have a case- 02358588, where the customer wants the gluster-related commands to be captured by the gluster sos plugin itself: - gluster vol info - gluster vol status - gluster peer status - gluster volume get <volname> all (for all volumes) - gluster get-state - "killall -USR1 glusterd" on the node where you see the problem and in one node without it to compare to see glusterd state info - "for gpid in $(ps aux | grep "glusterfs " | grep :_ | awk '{print $2}') ; do kill -USR1 $gpid ; done" on node with hanging VM to collect glusterfs state info - ps -Ll -p <pid of a zombie process> - cat /proc/<pid of a zombie process>/task/*/stack Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: