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.

https://beaker.engineering.redhat.com/tasks/executed?task=/CoreOS/selinux-policy/Regression/bz485078-wrong-context-for-sysstat&job_id=252821

Version-Release number of selected component (if applicable):
RHEL-7.0-20120620.n.0

Steps to Reproduce:
* get a ppc64 machine with RHEL-7.0 installed
* run following automated test on the machine:
  /CoreOS/selinux-policy/Regression/bz485078-wrong-context-for-sysstat

Actual results:
# sar -y
Requested activities not available in file /var/log/sa/sa25

Expected results:
* sar -y produces the same output on all architectures

Sorry, here is the URL where you can see the problem:

http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2012/06/2528/252821/538648/6550667/TESTOUT.log

Hi Milos,

please, what's the content of the /proc/tty/driver/serial file?
And what's the output of this command? (needs to be run as root):
# sar -y 1 1

Was that a virtual machine? There may be a problem with some virtual machines, see bug #715300

Thanks,

peter

Hi Milos,

I've tried RHEL-7.0-20120711.2, ppc64 on ibm-p730-02-lp1.rhts.eng.bos.redhat.com machine.

Content of /proc/tty/driver/serial file is following:
# cat /proc/tty/driver/serial
serinfo:1.0 driver revision:
0: uart:unknown port:00000000 irq:0
1: uart:unknown port:00000000 irq:0
2: uart:unknown port:00000000 irq:0
3: uart:unknown port:00000000 irq:0

what means, that there are no statistics available for sar.

So.. this is not a sysstat bug. But I can't tell whether it is notabug or bug for kernel or something..

I haven't seen the error message for a long time. Maybe it's fixed. Because it seems not to be a sysstat bug we can close it as NOTABUG. If I encounter the error message again, I will report it against kernel and I will add you to CC list.

I agree. Closing as NOTABUG. Thanks.