Bug 102445 - sysstat's sar reports wrong values in case of reboot
Summary: sysstat's sar reports wrong values in case of reboot
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: sysstat
Version: 1.0
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-08-15 07:35 UTC by Oliver Paukstadt
Modified: 2007-04-18 16:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-01-27 12:25:09 UTC
Embargoed:


Attachments (Terms of Use)

Description Oliver Paukstadt 2003-08-15 07:35:44 UTC
Rebooting a box causes sysstat sar to report wrong data about the moment of reboot.
This is because RedHat linux does not write the Linux-Reboot record (dummy
record) to the sysstat statistics file. This causes wrong values if the data is
evaluated later because most values decrease in case of reboot.

sadc.c source says about the problem:
/*
 ***************************************************************************
 * sadc called with interval and count parameters not set:
 * write a dummy record notifying a system restart.
 * This should typically be called this way at boot time,
 * before the cron daemon is started to avoid conflict with sa1/sa2 scripts.
 ***************************************************************************
 */

To fix, add something like

[ -e /usr/lib/sa/sadc -a -x /usr/lib/sa/sadc ] && /usr/lib/sa/sadc

to rc.sysinit after it is clear /var is mounted (at least when the other
activities on /var start).

Comment 1 Greg Edwards 2003-11-17 17:41:35 UTC
This is because the rpm does not contain the /etc/init.d/sysstat
script (sysstat.sh in the tarball).  It needs to be patched to play
nice with chkconfig.  Other than that, just a few lines in the spec
file will fix this.

Comment 2 Nils Philippsen 2004-01-13 16:20:20 UTC
I consider this for future product versions.

Comment 3 Nils Philippsen 2004-01-27 12:25:09 UTC
fixed in 5.0.0-0.6


Note You need to log in before you can comment on or make changes to this bug.