Can't run vmsat or sar commands 1

[wpdavids]

For some reason on a particular system that I maintain vmstat or sar will not run. The error messages are below.

# vmstat 5 40
exec(): 0509-036 Cannot load program vmstat because of the following errors:
0509-023 Symbol vmgetinfo in vmstat is not defined.
0509-026 System error: Cannot run a file that does not have a valid form
at.
# sar 5 40
sar: A system call received a parameter that is not valid

How can I fix this problem, has any one seen a situation like this ?

 

[aixqueen]

check that the filesets are loaded?

# which_fileset vmstat
/usr/bin/vmstat bos.acct 4.3.3.0
/usr/ucb/vmstat -> /usr/bin/vmstat bos.compat.links 4.3.1.0


# lslpp -l | grep bos.acct
bos.acct 4.3.3.26 COMMITTED Accounting Services
bos.acct 4.3.3.0 COMMITTED Accounting Services

My guess is you migrated and you have an old copy of the program on your system...o
or the program is not loaded at all...

 

[prv3116]

There was a fix we had to install because of sar errors. sar would run, like with sar 1 100, but would periodically give us negative output readings. I checked the apar database and I think it was IY10331.

 

[Janghyegyung]

I got another error messages about running vmstat and sar command..

# vmstat 2 3
kthr memory page faults cpu
----- ----------- ------------------------ ------------ -----------
r b avm fre re pi po fr sr cy in sy cs us sy id wa
read: No such device or address

# sar 2 3
sadc: : Operation not supported on socket
Versions of sadc and sar are inconsistent.

How can I fix this problem?

 

[aixqueen]

Some things to check..

Check your levels of the software and if they are installed as stated above
vs what is on the machine...
Is you machine at 4.3.2 but your bos. acct at a lower level...? or vice versa?

Are you pointing to an older version of the sar and vmstat...as in you did an upgrade...but the path takes the older one first? .check to see which one you are executing? See if there are two versions on your machine with the find command...and see which one you are executing...with the which command

lppchk -v lppchk -c look for broken filesets...
When was the machine last rebooted?

As mentioned above there were a lot of patches on bos.acct..........

 

[aixnag]

mostly it looks like

version conflict problem. please check your OSlevel and check the file vmstat level aslo using lppchk -v .

bye
nagaraj (aix specialist)

 

[bjverzal]

This also happens after you install a ptf to this fileset and do not reboot.

Bill.

 

[jprabaker]

Check that you have the following linked file:

unix -> /usr/lib/boot/unix_?? - where ?? is either mp or up depending on if you have a multi processor system.

If not issue the following command:

ln -fs /usr/lib/boot/unix_?? /unix

Regards,

 

[Janghyegyung]

Thanks, Bill.

As you said, I applied ML07 and did not reboot the server. When doing some actions, I did reboot togegher and vmstat and sar is OK..

After installing ptf, will reboot, I see. Thank you.

 

[Janghyegyung]

I got the answer for the problem executing vmstat in this thread, and found another server that has the same case.

# oslevel
4.3.0.0

# lslpp -l bos.acct
Fileset Level State Description
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
bos.acct 4.3.2.1 COMMITTED Accounting Services

Path: /etc/objrepos
bos.acct 4.3.1.0 COMMITTED Accounting Services

This is the problem about consistency oslevel and bos.acct's level?