Link to home
Start Free TrialLog in
Avatar of damonmanni
damonmanni

asked on

Getting Bus Error when running TOP command on Solaris 10

Hello EE,

- I am getting a "bus error" when executing the "top" command.  
- I have run several other cmds such as vmstat, iostat, df -k, ls, du, etc... just to see if they too would generate a bus error also, but no problems found.  
- I also ran mpstat which reported no problem either.  All done to rule out any possible h/w and OS incompatability.
- I have not seen any related errors in: /var/log/syslog

- I am running this version of Solaris:
# cat /etc/release
                       Solaris 10 5/09 s10s_u7wos_08 SPARC
           Copyright 2009 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                             Assembled 30 March 2009

- uname -a
SunOS devsrv  5.10 Generic_141414-10 sun4u sparc SUNW,Sun-Fire-V440

- Here is the top version - /usr/local/bin/top -v
top: version 3.8beta1

Any insight on what this problem may be and or how to dig further would be much appreciated.

cheers,
Damon
Avatar of jgiordano
jgiordano
Flag of United States of America image

What do you get in /var/dam/messages @ the time the command is run? Can you Post the bus error?

Can you run prtdiag -v and prtconf -v and see if the errors
Avatar of damonmanni
damonmanni

ASKER

Hello and thanks for the quick feedback.  Here are more results:


1. No msgs seem to be appearing in /var/adm/messages when I execute the top command.  It is a  zero length file.  Hmmm.  But, don't think this is too critical as I believe this svr has been running for some time now.

2. If I run 'top', it comes back with:
Bus Error
 - and then the SHELL gets funky also in that CR/LF stop working; if I type a command like "ls" and hit return, it does not echo back the "ls" but does execute the cmmd and I do see the o/p (file list).

3.  I can run ptrdiag & ptr conf with success.  I went thru both lengthly outputs and did not see any errors or possible  problems sticking out at me.

Any other thoughts?  Could it be anything to do with the version of top we are using:
top: version 3.8beta1

cheers,
Damon
ASKER CERTIFIED SOLUTION
Avatar of jgiordano
jgiordano
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of omarfarid
how you got top installed on your system? what is your system architecture? please run

uname -m
Well I was working on your advice in reinstalling top, but now it is running successfully again.  hmmm...  I don't know the history of this box but it is running Solaris 10, Oracle and ZFS cache.  So, I suspect some appl consumed alot of memory quickly and the kernel did not have enough memory left to run top.  Not sure but I just suspect resource contention due to an appl usage.

If I find out more I will post back.