We have had some issues with our ESX servers where vCenter lost connection to them. It appears we are not the only one:
http://communities.vmware.com/message/1138787#1138787
http://www.ntpro.nl/blog/archives/860-Abnormally-increased-RAM-usage-of-hostd.html
So it appears the vmware-hostd had a memory leak.
Now we want to be in control and determine ourselves to restart the hostd process, but we do not run it against all server blindly. We needed a list first which tell us what servers are running high with hostd memory usage. Since vmware-hostd is a service console process, powershell wasn't really an option. So I used plink and dos batch scripting instead, giving me a perfect .csv list with the current memory usage on each server.
Check it out (part of the README-FIRST.TXT):
"Hi all,
This is a new nifty script to get the current memory usage of the vmware-hostd process.
What you need to do:
- Download plink.exe from the web (use google or: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)
Put it in the same directory where all the scripts are (and where you should find this README-FIRST.TXT)
- Fill the 'servers.txt' file with your ESX servers - ipaddress/dns name - each server on each line.
Like:
esxserver01
esxserver02
esxserver03
etc.
- Replace the <password> <username> with a username and password which allows you to log on to your ESX server. It does not need to be root, also non-admin users should be able to run 'ps'. Alter the file: 'doaction.cmd' and 'trust.cmd'.
- Start 'startscript.cmd' FROM THE COMMANDLINE! So run 'cmd', cd to the dir where all these scripts are.
- If you are getting questions to accept the key file run 'startalltrust.cmd', it will use 'input.txt' file to provide a 'y' to all those key thingies.
- You should get result.csv with <servername>,<hostd memory usage>
"
|
Download Get vmware-hostd mem-usage
