cancel
Showing results for 
Search instead for 
Did you mean: 

5230 "top" results seem awfully odd...

elanmbx
Level 6

In fact, so odd that I'm disinclined to believe that they are accurate.  If they were, this system should not even be functioning.  Has anyone run across this?

5230 recently upgraded to 2.7.3

top - 19:26:48 up 10 days, 6:01, 2 users, load average: 569.26, 568.91, 565.18
Tasks: 1286 total, 1 running, 1285 sleeping, 0 stopped, 0 zombie
Cpu(s): 10.2%us, 1.1%sy, 0.0%ni, 88.3%id, 0.3%wa, 0.0%hi, 0.1%si, 0.0%st
Mem: 131931128k total, 131035864k used, 895264k free, 19784k buffers
Swap: 68272124k total, 12808224k used, 55463900k free, 65896500k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
57751 root 20 0 55.8g 43g 3316 S 256.6 34.4 19978:13 spoold
153046 root 20 0 753m 256m 224m D 12.6 0.2 15:45.28 bpbkar
153014 root 20 0 735m 531m 517m D 8.7 0.4 14:25.37 bpbkar
58249 rabbitmq 20 0 2581m 41m 2124 S 3.6 0.0 489:59.55 beam.smp
295519 root 20 0 14076 2136 868 R 2.6 0.0 0:04.32 top
291553 maintena 20 0 14076 2144 868 S 2.3 0.0 0:18.15 top
56913 root 20 0 3523m 16m 2116 S 1.0 0.0 149:07.23 nbappdbsrv
23574 root 15 -5 0 0 0 S 0.3 0.0 67:11.39 vxfs_thread
25629 root 20 0 0 0 0 S 0.3 0.0 14:52.27 kondemand/0

1 REPLY 1

elanmbx
Level 6

Well, there was def something strange going on with this appliance - had a bunch of hung VMware jobs this morning, and the few NFS mounts on the system were not responding when I ran "df"...

Scheduled and performed a reboot - system hung really good when trying to unmount the NFS.  Had to performa a hard reset on the appliance.

Good news is that it came up fine and things appear to be back to normal.