Good day everyone,

I came across an unusual problem with `sar' utility included in
bos.acct package with AIX. It does not show correct results, while
'sa1' and 'sa2' scripts are being run as per default system setup.

[quote su - adm -c 'crontab -l']
0 8-17 * * 1-5 /usr/lib/sa/sa1 1200 3 &
0 * * * 0,6 /usr/lib/sa/sa1 &
0 18-7 * * 1-5 /usr/lib/sa/sa1 &
5 18 * * 1-5 /usr/lib/sa/sa2 -s 8:00 -e 23:01 -i 3600 -ubcwyaqvm &
[unquote]

First two-three scheduled runs of sa1 gives corerct results, but
afterwards something happens and sar produces following:

[quote sar]

AIX dbsrv1 3 5 00CEFDDE4C00 04/20/05

System configuration: lcpu=4 ent=2.00

00:00:00 %usr %sys %wio %idle physc %entc

System configuration changed. The current iteration values may be
inaccurate.

sar: There is not enough memory available now.
[unquote]

AIX 5.3ML1 is running in an LPAR of a p570 server. Same happens to
second partition, no difference. Maybe bos.acct cannot be used in
LPARs? I've been using this package to provide system load ststistics
for quite a while, since AIX4.2.0/IBM POWERRSTATION 390 and
AIX3.2.5/7009-C10 with AIX 4.2.0 times, still using it on AIX
4.3.3/7025-F50, as well as on AIX 5.1/7025-6F0 with no troublre at
all.

Anyone got any hints/clues?


Alexey

Alex wrote:
> Good day everyone,
>
> I came across an unusual problem with `sar' utility included in
> bos.acct package with AIX. It does not show correct results, while
> 'sa1' and 'sa2' scripts are being run as per default system setup.
>
> [quote su - adm -c 'crontab -l']
> 0 8-17 * * 1-5 /usr/lib/sa/sa1 1200 3 &
> 0 * * * 0,6 /usr/lib/sa/sa1 &
> 0 18-7 * * 1-5 /usr/lib/sa/sa1 &
> 5 18 * * 1-5 /usr/lib/sa/sa2 -s 8:00 -e 23:01 -i 3600 -ubcwyaqvm &
> [unquote]
>
> First two-three scheduled runs of sa1 gives corerct results, but
> afterwards something happens and sar produces following:
>
> [quote sar]
>
> AIX dbsrv1 3 5 00CEFDDE4C00 04/20/05
>
> System configuration: lcpu=4 ent=2.00
>
> 00:00:00 %usr %sys %wio %idle physc %entc
>
> System configuration changed. The current iteration values may be
> inaccurate.
>
> sar: There is not enough memory available now.
> [unquote]
>
> AIX 5.3ML1 is running in an LPAR of a p570 server. Same happens to
> second partition, no difference. Maybe bos.acct cannot be used in
> LPARs? I've been using this package to provide system load ststistics
> for quite a while, since AIX4.2.0/IBM POWERRSTATION 390 and
> AIX3.2.5/7009-C10 with AIX 4.2.0 times, still using it on AIX
> 4.3.3/7025-F50, as well as on AIX 5.1/7025-6F0 with no troublre at
> all.
>
> Anyone got any hints/clues?
>
>
> Alexey

sar has issues with micro partitioning / shared processor partitions.
There is an efix.

Greg.

As Greg already wrote there are issues with micropartitioning. You
can use an efix or disable micropartitioning with "smtctl -m off"

I would take a look in /var/adm/sa most probably there are some
logfiles
with several hundred MB in size (not used in the FS - spares i think).

On 29 Apr 2005 08:18:50 -0700, "sllabres" <sllabres@baden-online.de>
wrote:

>As Greg already wrote there are issues with micropartitioning. You
>can use an efix or disable micropartitioning with "smtctl -m off"
>
>I would take a look in /var/adm/sa most probably there are some
>logfiles
>with several hundred MB in size (not used in the FS - spares i think).

Thank you very much for pointing me to the right direction (I hope), I
did have a look at /var/adm/sa directory, there were several files
with 5-15 MB size, nothing unusual for an AIX system from my point of
view. I will try to locate an e-fix now. Local IBM dealers/support
told me they 'filed' and issue with IBM but they are not sure how lon
it will take to fix.


Regards

Alexey

On Thu, 28 Apr 2005 17:32:02 -0400, Greg <no@spam.com> wrote:

>Alex wrote:
>> Good day everyone,
>>
>> I came across an unusual problem with `sar' utility included in
>> bos.acct package with AIX. It does not show correct results, while
>> 'sa1' and 'sa2' scripts are being run as per default system setup.
>>
>> [quote su - adm -c 'crontab -l']
>> 0 8-17 * * 1-5 /usr/lib/sa/sa1 1200 3 &
>> 0 * * * 0,6 /usr/lib/sa/sa1 &
>> 0 18-7 * * 1-5 /usr/lib/sa/sa1 &
>> 5 18 * * 1-5 /usr/lib/sa/sa2 -s 8:00 -e 23:01 -i 3600 -ubcwyaqvm &
>> [unquote]
>>
>> First two-three scheduled runs of sa1 gives corerct results, but
>> afterwards something happens and sar produces following:
>>
>> [quote sar]
>>
>> AIX dbsrv1 3 5 00CEFDDE4C00 04/20/05
>>
>> System configuration: lcpu=4 ent=2.00
>>
>> 00:00:00 %usr %sys %wio %idle physc %entc
>>
>> System configuration changed. The current iteration values may be
>> inaccurate.
>>
>> sar: There is not enough memory available now.
>> [unquote]
>>
>> AIX 5.3ML1 is running in an LPAR of a p570 server. Same happens to
>> second partition, no difference. Maybe bos.acct cannot be used in
>> LPARs? I've been using this package to provide system load ststistics
>> for quite a while, since AIX4.2.0/IBM POWERRSTATION 390 and
>> AIX3.2.5/7009-C10 with AIX 4.2.0 times, still using it on AIX
>> 4.3.3/7025-F50, as well as on AIX 5.1/7025-6F0 with no troublre at
>> all.
>>
>> Anyone got any hints/clues?
>>
>>
>> Alexey
>
>sar has issues with micro partitioning / shared processor partitions.
>There is an efix.
>
>Greg.


I have found and applied the e-fix and it works fine now, thank you
very much everyone!

Alexey