'Top' utility floating point error
 

Have a strange problem here. On a pretty much "stock" installation of RH 7.2, I can't run the 'top' command. I figured perhaps if I could find the rpm that provides 'top' to begin with, then perhaps a forced reinstall would work. Unfortunately, I can't seem to find that. The closest I get is libgtop, and it seems to provide the related libraries, but not the binary. Also, the one of the machines in the environment is able to run 'top' w/o the libgtop package (accoring to rpm-qa | grep libgtop), so there goes my theory there.

Anyhow, this is the error I get:

5:44pm up 428 days, 3:04, 1 user, load average: 0.03, 0.04, 0.00
37 processes: 36 sleeping, 1 running, 0 zombie, 0 stopped
Floating point exception
[user@server2 user]$
[user@server2 user]$
[user@server2 user]$ rpm -qa | grep libgtop
libgtop-1.0.12-4

Anyone have any suggestions for me? I could really use the help.

The rpm is in procps-*
but that may not fix your problem, as I am having it too.

What is even stranger is that top started working again for a while. I just assumed our cranky sysadmin had fixed it himself, but didn't tell anyone (as usual). I found later than again, it started happening again. I am now completely at a loss as to how this could only happen intermittantly. I get a "floating point" error on 4 different machines that are set up almost identically.

If anyone has any ideas other than just re-installing the default package or even installing an updated one, please let me know...

thx.

I am that cranky system admin, and I tried reinstalling it and no dice. The only other thing I could think would be a reboot, but that isn't going to happen. Not when uptime is everything and some of these systems are going on 1.5 years worth of uptime.

I will keep trying though.

MIKE

haha... just the fact that you're replying on this means that you aren't as cranky as our sysadmin!

I really do appreciate the assist on this, and yes, uptime is important. I suppose if the reboot is the true solution here, then so be it... I could advise on scheduling one if necessary.

Before that though, I think I'll see if I can figure out what's really wrong.