Red Hat Bugzilla – Bug 887231
[abrt] sysstat-9.0.4-20.el6: Process /usr/bin/sar was killed by signal 11 (SIGSEGV)
Last modified: 2016-09-22 04:51:07 EDT
Description of problem:
sysstat getting crash randomly
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.run the below command
$ /usr/bin/sar -A -f /var/log/sa//sa13
2. occur randomly
it gets crash
it should not get crash
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Created attachment 780524 [details]
what's the status of this bug? I see customer case is closed. Would it be possible to get the problematic sa daily data file from customer, if he is still able to reproduce the issue?
Upstream fix can be found here, but without any note on reproducer:
I would like to see the patch backported in RHEL-6, but I would rather avoid manually modifying sa files for reproducer purposes..
I wasn't able to reproduce the bug even by modifying the sa daily data file, thus I'm closing this bug as INSUFFICIENT_DATA. In case you have any information which could help reproduce the bug, or you came across it again, feel free to reopen this bug.
I can verify that attached sa data file crashes sysstat and that attached patch fixes the crash. I'm proposing this bug for RHEL-6.8, but this late in the cycle, I can't guarantee that it'll be fixed. If this bug is important for you, please talk to the PM.
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.
*** Bug 1355621 has been marked as a duplicate of this bug. ***