Hi I have afuny case that I have 2 sun blade 2000 machine, running Solaris 8 and when entered sar command in one machine it working, in anther one reported as (( <<<<ksh: sar: not found>>>>)). By using find tools also the command not found!! Note that I do the same scenario in both machines!!! So please do you have any explanation? Thanks and Regard -----Original Message----- From: Eric Paul [mailto:epaul@profitlogic.com] Sent: Wednesday, April 14, 2004 5:53 PM To: Subject: SUMMARY: sar not working in Solaris 9 on V880 or V240 Many thanks to everyone who replied. On Darren Dunham's suggestion, I trussed the running cron pid and found that it was having pam troubles. After some googling, I was able to come across some sunforum posts saying that somewhere along the line, Sun changed how PAM behaves in Sol 9. I added these lines to pam.conf: cron account required pam_projects.so.1 cron account required /usr/lib/security/pam_unix.so.1 And restarted cron. NOTE: You MUST restart cron. I made the changes to pam.conf and did not restart cron, and was still seeing it not working. So after all this, it turned out to be not a SAR problem, not even really a CRON problem, but a PAM problem :P Many jeers to: Pohl, Stefan [Stefan.Pohl@Dresdner-Bank.com] Kulkarni Pawan-W19278 [Pawz@motorola.com] Obst, Thomas [Thomas.Obst@t-mobile.de] Ian Pease [I.Pease@esteem.co.uk] Broderick, Sean [Sean.Broderick@irl.xerox.com] for not having properly configured auto-responders! May a million spambots chew on their emails!! -----Original Message----- From: sunmanagers-bounces@sunmanagers.org [mailto:sunmanagers-bounces@sunmanagers.org]On Behalf Of Eric Paul Sent: Wednesday, April 14, 2004 10:01 AM To: sunmanagers@sunmanagers.org Subject: UPDATE: sar not working in Solaris 9 on V880 or V240 Thanks to everyone who has responded so far. The suggestions have been good sanity checks, but so far no one has figured out the problem. Here is some additional information. - If I "su - sys" and manually run /usr/lib/sa/sa1, it works fine. So it appears to be a problem in cron. - If I try adding a truss to the cronjob, I get no results back. If I tell truss to output to a file "/bin/truss -f -o /tmp/trace /usr/lib/sa/sa1" the file never gets created. Ditto without the -f. Ditto if I don't use -o and just use >>. - I received many suggestions saying that cron wasn't running for a number of reasons. /var/cron/log shows my jobs being executed. The user can run cron jobs. I have tried changing the password in /etc/shadow to all manner of things, no difference. - Syslog shows nothing. No mails are being generated, not to root, not to sys. - I received one suggestion saying there was a problem with openssh on sol9, and that I should only change the sys crontab from the console. I dragged my laptop over and plugged into the serial port. No dice. - I received a suggestion telling me about a problem with the Virtual SCSI Device Driver on V240s. I can't see that I am loading that. # pkginfo |grep SCSI system SUNWfcp Sun FCP SCSI Device Driver system SUNWfcpx Sun FCP SCSI Device Driver (64-bit) system SUNWses SCSI Enclosure Services Device Driver system SUNWsesx SCSI Enclosure Services Device Driver (64-bit) If anyone has further suggestions, I am open to anything at this point. Thanks! Eric -----Original Message----- From: sunmanagers-bounces@sunmanagers.org [mailto:sunmanagers-bounces@sunmanagers.org]On Behalf Of Eric Paul Sent: Tuesday, April 13, 2004 4:56 PM To: sunmanagers@sunmanagers.org Subject: sar not working in Solaris 9 on V880 or V240 Ok, I have a problem that is stumping myself and the other admin here. We just got some new servers in, a couple of V880s and some V240s. We installed Solaris 9 on them (12/03 on the V240, 06/03 on the V880 when we saw problems on the 240) For some reason, sar is not working as it does everywhere else. I am using the same crontab entries that I have working on a V120 running Sol 9, and still no dice. It starts up fine, but the incremental updates don't seem to be happening. Here are the relevant files and info: # cat /var/spool/cron/crontabs/sys #ident "@(#)sys 1.5 92/07/14 SMI" /* SVr4.0 1.2 */ # # The sys crontab should be used to do performance collection. See cron # and performance manual pages for details on startup. # # 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 00,05,10,15,20,25,30,35,40,45,50,55 * * * * /usr/lib/sa/sa1 01 00 * * * /usr/lib/sa/sa1 59 23 * * * /usr/lib/sa/sa1 01 00 * * * find /var/adm/sa -name "sa*" -type f -ctime +15 -exec rm -f {} \; # cat /etc/rc2.d/S21perf #!/sbin/sh # # Copyright (c) 1984, 1986, 1987, 1988, 1989 AT&T. # All rights reserved. # # THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF AT&T # The copyright notice above does not evidence any # actual or intended publication of such source code. # # Copyright (c) 1997 by Sun Microsystems, Inc. # All rights reserved. # #ident "@(#)perf.sh 1.7 97/12/08 SMI" # Uncomment the following lines to enable system activity data gathering. # You will also need to uncomment the sa entries in the system crontab # /var/spool/cron/crontabs/sys. Refer to the sar(1) and sadc(1m) man pages # for more information. if [ -z "$_INIT_RUN_LEVEL" ]; then set -- `/usr/bin/who -r` _INIT_RUN_LEVEL="$7" _INIT_RUN_NPREV="$8" _INIT_PREV_LEVEL="$9" fi if [ $_INIT_RUN_LEVEL -ge 2 -a $_INIT_RUN_LEVEL -le 4 -a \ $_INIT_RUN_NPREV -eq 0 -a \( $_INIT_PREV_LEVEL = 1 -o \ $_INIT_PREV_LEVEL = S \) ]; then /usr/bin/su sys -c "/usr/lib/sa/sadc /var/adm/sa/sa`date +%d`" fi # sar SunOS dev-app-s00 5.9 Generic_112233-11 sun4u 04/13/2004 16:04:55 %usr %sys %wio %idle 16:04:55 unix restarts 16:14:00 unix restarts 16:15:00 1 2 7 91 # date Tue Apr 13 16:50:19 EDT 2004 # cat /var/cron/log ! *** cron started *** pid = 164 Tue Apr 13 16:14:01 2004 ! unexpected pid returned 174 (ignored) Tue Apr 13 16:14:02 2004 > CMD: /usr/lib/sa/sa1 > sys 295 c Tue Apr 13 16:15:00 2004 < sys 295 c Tue Apr 13 16:15:00 2004 > CMD: /usr/lib/sa/sa1 > sys 328 c Tue Apr 13 16:20:00 2004 < sys 328 c Tue Apr 13 16:20:00 2004 ts=13 > CMD: /usr/lib/sa/sa1 > sys 333 c Tue Apr 13 16:25:00 2004 < sys 333 c Tue Apr 13 16:25:00 2004 ts=13 > CMD: /usr/lib/sa/sa1 > sys 335 c Tue Apr 13 16:30:00 2004 < sys 335 c Tue Apr 13 16:30:00 2004 ts=13 > CMD: /usr/lib/sa/sa1 > sys 340 c Tue Apr 13 16:35:00 2004 < sys 340 c Tue Apr 13 16:35:01 2004 ts=13 > CMD: /usr/lib/sa/sa1 > sys 346 c Tue Apr 13 16:40:00 2004 < sys 346 c Tue Apr 13 16:40:00 2004 ts=13 > CMD: /usr/lib/sa/sa1 > sys 355 c Tue Apr 13 16:45:00 2004 < sys 355 c Tue Apr 13 16:45:00 2004 ts=13 > CMD: /usr/lib/sa/sa1 > sys 363 c Tue Apr 13 16:50:00 2004 < sys 363 c Tue Apr 13 16:50:00 2004 ts=13 There are no error messages in syslog or in my mail. Any ideas? TIA! I will summarize. Eric _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Thu Apr 15 12:32:13 2004
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:31 EST