Instead let's run 'kmem -z'.  This should be more useful and it is not nearly as expensive.

(In reply to Dave Wysochanski from comment #1)
> Instead let's run 'kmem -z'.  This should be more useful and it is not
> nearly as expensive.

Scratch the above.  We don't know how long this will take to run and it may be best to just get the vmcore in the hands of the engineer analyzing as fast as possible.

FWIW, this came as a result of the following bz:
https://bugzilla.redhat.com/show_bug.cgi?id=1073987#c13

If we want, we could re-think another kmem command to run by default but we need to weigh cost (execution time) vs benefit (how many people/cores find it useful).  In absence of good data, for now let's just leave the kmem commands out by default.

(In reply to Dave Wysochanski from comment #3)
> FWIW, this came as a result of the following bz:
> https://bugzilla.redhat.com/show_bug.cgi?id=1073987#c13
> 
> If we want, we could re-think another kmem command to run by default but we
> need to weigh cost (execution time) vs benefit (how many people/cores find
> it useful).  In absence of good data, for now let's just leave the kmem
> commands out by default.

Agreed.

This looks fixed to me in retrace-server-1.11-2.el6.noarch

retrace-server-1.12-2.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/retrace-server-1.12-2.el6

Package retrace-server-1.12-2.el6:
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing retrace-server-1.12-2.el6'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-2089/retrace-server-1.12-2.el6
then log in and leave karma (feedback).

retrace-server-1.12-2.el6 has been pushed to the Fedora EPEL 6 stable repository.  If problems still persist, please make note of it in this bug report.