Hide Forgot
Description of problem: The sadc/sar utilities provided via sysstat are 32bit versions. This creates problems on ppc64 based systems due to many of the values in /proc being 64bit based. The most noticeable behavior is when networking traffic exceeds the value of 4294967295. After that point, sar will start reporting zeros for those particular network stats. Version-Release number of selected component (if applicable): sysstat-7.0.2-3.el5 How reproducible: Consistent. As soon as a value (e.g. network bytes or packets) exceeds 4294967295, sar no longer sees any change in network statistics (as sscanf appears to cap the value to the maximum a 32bit long will hold). Steps to Reproduce: 1. Generate a lot of network traffic across the loopback device. For example: # dd if=/dev/zero bs=16k | ssh localhost dd of=/dev/null bs=16k 2. Periodically check the statistics with sar: # sar -n DEV 10 1 3. Wait until one of the values exceeds 4294967295 Actual results: Using rxbyt/s and txbyt/s as an example, before the values reach 4294967295, you get sar output like the following: 10:13:21 AM IFACE rxpck/s txpck/s rxbyt/s txbyt/s rxcmp/s txcmp/s rxmcst/s 10:13:31 AM lo 2509.51 2509.51 13279936.74 13279936.74 0.00 0.00 0.00 Afterwards, the stats that have exceeded 4294967295 drop to zero. For example, /proc/net/dev reports the following: # cat /proc/net/dev Inter-| Receive | Transmit face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed lo:4449003660 843105 0 0 0 0 0 0 4449003660 843105 0 0 0 0 0 0 ... # cat /proc/net/dev Inter-| Receive | Transmit face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed lo:5860333612 1107681 0 0 0 0 0 0 5860333612 1107681 0 0 0 0 0 0 ... But sar shows this: 10:14:05 AM IFACE rxpck/s txpck/s rxbyt/s txbyt/s rxcmp/s txcmp/s rxmcst/s 10:14:15 AM lo 2510.81 2510.81 0.00 0.00 0.00 0.00 0.00 Expected results: Sar should continue to track actual traffic.
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 unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Hi Kevin, please, try to install ppc64 version of sysstat and let me know whether that worked for you: # yum install sysstat.ppc64 Thanks, peter
From what repository? The standard RHEL5 repository does not contain sysstat.ppc64: # yum install sysstat.ppc64 Loaded plugins: katello, product-id, rhnplugin, security, subscription-manager Updating certificate-based repositories. Unable to read consumer identity Setting up Install Process No package sysstat.ppc64 available. Nothing to do # yum repolist Loaded plugins: katello, product-id, rhnplugin, security, subscription-manager Updating certificate-based repositories. Unable to read consumer identity repo id repo name status rhel-ppc-server-5 Red Hat Enterprise Linux (v. 5 for 64-bit IBM POWER) 13418 repolist: 13418 # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.8 (Tikanga)
I see, thanks. Sysstat.ppc64 should be available in ppc repository, I am reassigning this to relegen.
Hi, I've created bug 824822 for inclusion in compose. Because it belongs to different QE team I also leave this in systat component. Here should be verified if 64-bit variant works and in rel-eng that it is properly distributed.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Removing reopened keyword as this bug was closed by mistake.
I'm closing this bug as the problem should be already addressed in the bug 824822 and it is too late in the RHEL-5 development cycle for us to verify it in the coming RHEL-5 minor release.