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.

Description of problem:

Same issue as described in URL below.  No answer given to the actual question of the tens of thousands.  They describe as "counters somewhere have overflown" but no fix or instructions shown for how to deal with that type of situation.

https://github.com/sysstat/sysstat/issues/8

Version-Release number of selected component (if applicable):

sysstat-9.0.4-27.el6.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Run CPU-intensive jobs (in our case oracle)
2. Run pidstat for a few hours
3. Reports have occurrences of impossibly-high resources

Actual results:

Example command:

for i in `seq 1 24`; do
  /usr/bin/pidstat -duhIl 30 118 >> $_filename
done

Report output:

1462942863     32714 4847.07 1792.37    0.00 1678.60     0  23596.53      0.00      0.00  oraclepldsc (LOCAL=NO)

Expected results:

System has only 4x CPUs, so I would expect 6th column to be max 400%, but since we have -I option I would not expect more than 100%.  This is not explained in the FAQ section 4.4.  We are also dividing by total # CPUs with the -I option.

Additional info:

This happens every time we use pidstat.

Bryan,

this issue should be fixed in RHEL-6.8 with sysstat-9.0.4-31.el6; we backported following patch: https://github.com/sysstat/sysstat/issues/73

peter

Thanks that's very good news.