Hot answers tagged htop
There is top's secure mode, when it is invoked as top -s In that mode the user can't change the refresh delay of top, kill or renice processes. If you want to make it system wide instead of on a per-invocation basis, you may use the /etc/toprc file with the following contents: s 3.0 Only two lines: first one to set secure-mode, and the second to set ...
You still have memory to spare. The system isn't swapping out cause it hasn't needed to yet... but then again, I notice something odd - from what I can tell, you have no swap space set up. On one of my (linux) systems it reads CPU[|||||||||||||||||||| 63.2%] Tasks: 89, 114 thr; 1 running Mem[||||||||||||||||| 167/1001MB] Load average: ...
VIRT does not have anything to do with used memory (virtual or otherwise), but with used address-space, which is not as related as you might think. Modern operating systems (including OSX) have a feature called demand paging which works by telling the operating system to map a certain region of virtual address space to a file (such as a shared library/DLL). ...
Did you look at 00FAQ as was suggested by the error message? Question 8.6 describes exactly your situation and how to work around it. If you don't want to install the Kernel source on your machine, a workaround would be to install the lsof binary package pkg_add -r lsof
As the message reports, this a bug in kernel-level code. Those CPUs are stuck in a kernel code (vmx-cpu-0) that is not yield()ing control of the CPU for a long period of time. As far as what to do - open a ticket with VMware. vmx-cpu-0 looks like their code, but I'm not totally sure.
Generally, 60MB is enough leeway. You can check with cat /proc/sys/vm/min_free_kbytes. That will tell you the amount of free RAM the server thinks it needs, and it's typically around 64MB. A bit less than that is fine -- unless you have some strange I/O storm, the amount of free RAM needed is extremely small. If you use NFS heavily or have some kind of ...
This would be trivial using a tool like monit. check system myhost if cpu usage (system) > 80% for 4 cycles then alert if cpu usage (user) > 80% for 5 cycles then alert if cpu usage (wait) > 90% for 5 cycles then alert
If you suspect an I/O hog process, you can use iotop to find it. Recent versions of htop also have per process I/O stats, but you might need to configure htop to show that.
This is a known issue with ESX 4. Virtual machines display increased memory usage in vmware-guestd and vmwareservice.exe. The memory footprint of the process continues to increase until the available memory is drained and the process cannot allocate any memory. This issue is more prominent when the guest operating system has a large number of IP ...
Only top voted, non community-wiki answers of a minimum length are eligible