check the sos version on the machine, and it should have rhs in it to confirm the different RPM in our child channel. changelog in rpm: ----- Changelog: * Tue Sep 11 2012 Amar Tumballi <atumball> = 2.2-17.el6rhs.1 - Change gluster.py to send signal to glusterfs process directly instead of 'gluster volume status' command. Resolves: bz851175 - Capture statedump files in sosreport -----
the changes that have been made to sosreport gluster plugin are * send SIGUSR1 signal to all the glusterfs processes instead of volume statedump or volume status cli command.(with SIGUSR1, from all the glusterfs processes including the mount points, self-heal daemon, nfs server the statedump information is received). * All the statedump information is collected in the sosreport.
Please could someone post the patches for this feature to the sos-devel mailing list for review. As we discussed previously we do not want sos in RHS to diverge from upstream and it's important that the review starts early to ensure that we don't end up having to back things out at a later stage.
I guess this is not part of update 3. I still see glusterdumps not being part of the archive.
http://pkgs.devel.redhat.com/cgit/rpms/sos/commit/?h=rhs-2.0-rhel-6&id=705f21a7394717d810cca63573cb0b815abd54fa will make sure we post all the patches to sos-devel@ ML in future.
@Sac (for comment #7) did you do a yum upgrade of sos package? sos is a different RPM, and not part of glusterfs rpm set... Refer to one of the mail I have sent to storage-qa on sos package.
Amar, yes I had done yum update before this. Or is it that I download and sosreport separately? Do we have the sosreport version so that I can cross check. I am running: [root@rhs-client19 ~]# sosreport -v sosreport (version 2.2)
Verified with RPM: http://download.devel.redhat.com/brewroot/packages/sos/2.2/17.1.el6rhs/noarch/sos-2.2-17.1.el6rhs.noarch.rpm With the above RPM update sosreport now places the glusterdumps in sosreport archive under directory tmp/ in the archive.
I have opened another bug (https://bugzilla.redhat.com/show_bug.cgi?id=867346) to track where the glusterdump files go into. We will keep this bug in verified state.
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/RHSA-2012-1456.html