SUMMARY: sar collecting

The issue is unrelated to "sar".  The problem seem to be cron.  The /var/cron/log 
file indicated that cron can not run becuase of some crappy error:

CMD:/usr/lib/sa/sa1
...
!bad user (sys) 
...

Our Security products do not update the data field on the /etc/shadow file:
sys:NP:11744:1:90:60::21577:

chaging the 11744 to something else (copy and modify another user) and update the 
sys entry.  

That got the "sar" collection working.  However, the file still only creates one entry 
like before... I am going to let it run for a while and see what happends.  

Thanks.


> I set-up a system to gather SAR data on a Solaris 2.8 [4500] system. 
> However, I 
> don't seem to be collecting any data.  When running this command:
> 
> /usr/bin/su sys -c "/usr/lib/sa/sadc /var/adm/sa/sa`date +%d`"
> 
> I get a file under /var/adm/sa of the type sa19  #of type sa[1-31]
> 
> when doing "sar -f /var/adm/sa/sa19" all I get is something like this:
> 
> 15:37:13 %usr %sys %wio %idle
> 15:37:13    unix restarts
> 
> I only get one file for the time when I ran the command, the file does
> not grow in 
> size and does not get modify in any way.  How do I collect the actual
> data?  And 
> most important how do I view the record of data-collected.  
> 
> Below is the procedure I followed from one of the admin books:
> 
> Carlos Sevillano
> 
> How to Set Up Automatic Data Collection
> 1. Become superuser.   Edit the file /etc/init.d/perf and uncomment all
> lines:
> This version of the sadc command writes a special record that marks the
> time
> when the counters are reset to zero (boot time). The sadc output is put
> into the
> file sadd (where dd is the current date), which acts as the daily system
> activity
> record.
> 3. Edit the /var/spool/cron/crontabs/sys file (the system crontab file)
> and
> uncomment the following lines:
> # 0 * * * 0-6 /usr/lib/sa/sa1
> # 20,40 8-17 * * 1-5 /usr/lib/sa/sa1
> # 5 18 * * 1-5 /usr/lib/sa/sa2 -s 8:00 -e 18:01 -i 1200 -A
> The first entry writes a record to /var/adm/sa/sadd on the hour, every
> hour,
> seven days a week.   The second entry writes a record to
> /var/adm/sa/sadd twice 
> each hour during peak working hours: at 20 minutes and 40 minutes past
> the hour, 
> from 8 a.m. to 5  p.m., Monday through Friday.  Thus, these two crontab
> entries 
> cause a record to be written to /var/adm/sa/sadd every 20 minutes from 8
> a.m. to 5 
> p.m., Monday through Friday, and every hour on the hour otherwise. You
> can 
> change these defaults to meet your needs.



________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers