Sponsored Content
Operating Systems Linux SuSE SUSE 11.4 sar monitoring not run by default. Post 302544828 by devtakh on Friday 5th of August 2011 07:21:13 AM
Old 08-05-2011
SUSE 11.4 sar monitoring not run by default.

Hi,
I had installed sysstat package below on a SUSE 11.4 box. I can see the sysstat cron file listed under the directory /etc/sysstat. However, it looks like the sysstat sar monitor is never run at all and the daily sar files are not created under the directory /var/log/sa. The cron daemon is also running. Am I missing something? Below is my configuration and file listing

# cat /etc/SuSE-release
openSUSE 11.4 (i586)
VERSION = 11.4
CODENAME = Celadon

#rpm -qa | grep -i sysstat
sysstat-9.0.6.1-13.1.i586


# ls -lrt /etc/sysstat/
total 16
-rw-r--r-- 1 root root 6228 Feb 19 00:27 sysstat.ioconf
-rw-r--r-- 1 root root 282 Feb 19 00:27 sysstat
-rw-r--r-- 1 root root 387 Feb 19 00:27 sysstat.cron
 

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to run sar on Sun Solaris?

I want to get some information about system activity report on UNIX server. I want to use 'sar'. But it seems that report is binary code and can not be read. Please advise how to do it. Thanks. (2 Replies)
Discussion started by: duke0001
2 Replies

2. UNIX for Dummies Questions & Answers

how can i make sar command run forever ?

Hello all i found out about the sar command but when looking in the man pages there is no way to make sar working for ever .. only with some kind of interval . like sar 2 30 . my question is can i just run sar for ever ? (5 Replies)
Discussion started by: umen
5 Replies

3. SuSE

Unable to Run a script at startup in suse

Hi I have a script myscript.sh that needs to be run whenever the server boots. The script is actually logging Syslog-ng messages to sql server. I need to lauch it at startup I have copied the script in etc/init.d i have also added the link ln -s /etc/init.d/syslog-ng-mssql-pipe.sh... (5 Replies)
Discussion started by: SystemEng
5 Replies

4. SuSE

Suse 11 - How to run 'make'

I just installed gcc using Yast. When I run 'make', the command is not found. What should I do? #which gcc /usr/bin/gcc (2 Replies)
Discussion started by: fld2007
2 Replies

5. Shell Programming and Scripting

One script for Linux Monitoring-free, sar, vmstat, mpstat

HI , I am wrirting a script for checking the performance monitoring on Linux System when my application is running. I have to run a test for 30 minutes on some server and while the test is running i have to capture the perfromance metrics of Linux through vmstat , sar, mpstat, free. here is the... (3 Replies)
Discussion started by: Anamica
3 Replies

6. Solaris

Understanding & Monitoring CPU performance (Load vs SAR)

Hi all, Been reading a lot of the cpu load and its "analogy of it to car traffic path of expressway" From wiki Most UNIX systems count only processes in the running (on CPU) or runnable (waiting for CPU) states. However, Linux also includes processes in uninterruptible sleep states... (13 Replies)
Discussion started by: javanoob
13 Replies
SADC(8) 							Linux User's Manual							   SADC(8)

NAME
sadc - System activity data collector. SYNOPSIS
/usr/lib/sysstat/sadc [ -C comment ] [ -S { INT | DISK | SNMP | IPV6 | POWER | XDISK | ALL | XALL } ] [ -F ] [ -L ] [ -V ] [ interval [ count ] ] [ outfile ] DESCRIPTION
The sadc command samples system data a specified number of times (count) at a specified interval measured in seconds (interval). It writes in binary format to the specified outfile or to standard output. If outfile is set to -, then sadc uses the standard system activity daily data file, the /var/log/sysstat/sadd file, where the dd parameter indicates the current day. In this case, sadc will overwrite the file if it is from a previous month. By default sadc collects all the data available from the kernel. Exceptions are interrupts and disk data, for which the relevant options must be explicitly passed to sadc (see options below). When the count parameter is not specified, sadc writes its data endlessly. When both interval and count are not specified, and option -C is not used, a dummy record, which is used at system startup to mark the time when the counter restarts from 0, will be written. For exam- ple, one of the system startup script may write the restart mark to the daily data file by the command entry: /usr/lib/sysstat/sadc - The sadc command is intended to be used as a backend to the sar command. Note: The sadc command only reports on local activities. OPTIONS
-C comment When neither the interval nor the count parameters are specified, this option tells sadc to write a dummy record containing the specified comment string. This comment can then be displayed with option -C of sar. -F The creation of outfile will be forced. If the file already exists and has a format unknown to sadc then it will be truncated. This may be useful for daily data files created by an older version of sadc and whose format is no longer compatible with current one. -L sadc will try to get an exclusive lock on the outfile before writing to it or truncating it. Failure to get the lock is fatal, except in the case of trying to write a normal (i.e. not a dummy and not a header) record to an existing file, in which case sadc will try again at the next interval. Usually, the only reason a lock would fail would be if another sadc process were also writing to the file. This can happen when cron is used to launch sadc. If the system is under heavy load, an old sadc might still be run- ning when cron starts a new one. Without locking, this situation can result in a corrupted system activity file. -S { INT | DISK | SNMP | IPV6 | POWER | XDISK | ALL | XALL } Specify which optional activities should be collected by sadc. Some activities are optional to prevent data files from growing too large. The INT keyword indicates that sadc should collect data for system interrupts. The DISK keyword indicates that sadc should collect data for block devices. The SNMP and IPV6 keywords indicate respectively that SNMP and IPv6 statistics should be collected by sadc. The POWER keyword indicates that sadc should collect power management statistics. The ALL keyword is equivalent to speci- fying all the keywords above and therefore all previous activities are collected. The XDISK keyword is an extension to the DISK one and indicates that partition statistics should be collected by sadc in addition to disk statistics. This option works only with kernels 2.6.25 and later. The XALL keyword is equivalent to specifying all the key- words above (including keyword extensions) and therefore all possible activities are collected. Important note: The activities (including optional ones) saved in an existing data file prevail over those selected with option -S. As a consequence, appending data to an existing data file will result in option -S being ignored. -V Print version number then exit. ENVIRONMENT
The sadc command takes into account the following environment variable: S_TIME_DEF_TIME If this variable exists and its value is UTC then sadc will save its data in UTC time. sadc will also use UTC time instead of local time to determine the current daily data file located in the /var/log/sysstat directory. EXAMPLES
/usr/lib/sysstat/sadc 1 10 /tmp/datafile Write 10 records of one second intervals to the /tmp/datafile binary file. /usr/lib/sysstat/sadc -C Backup_Start /tmp/datafile Insert the comment Backup_Start into the file /tmp/datafile. BUGS
The /proc filesystem must be mounted for the sadc command to work. All the statistics are not necessarily available, depending on the kernel version used. sadc assumes that you are using at least a 2.6 kernel. FILES
/var/log/sysstat/sadd Indicate the daily data file, where the dd parameter is a number representing the day of the month. /proc contains various files with system statistics. AUTHOR
Sebastien Godard (sysstat <at> orange.fr) SEE ALSO
sar(1), sa1(8), sa2(8), sadf(1), sysstat(5) http://pagesperso-orange.fr/sebastien.godard/ Linux MAY 2012 SADC(8)
All times are GMT -4. The time now is 06:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy