Examining logs is an important way for debugging and troubleshooting a system. There are about ten log files in the ESX server for the hostd agent, which listens API calls, with the same naming pattern as hostd-?.log under the /var/log/vmware directory. The hostd-index file has the number of currently used log files.
The log entry has a similar format to that of VC server logs. Following is a quick sample:
Bothered by SLOW Web UI to manage vSphere? Want to manage ALL your VMware vCenters, AWS, Azure, Openstack, container behind a SINGLE pane of glass? Want to search, analyze, report, visualize VMs, hosts, networks, datastores, events as easily as Google the Web? Find out more about vSearch 3.0: the search engine for all your private and public clouds.
[2008-06-21 07:24:40.769 ‘SOAP’ 64834480 trivia] Received soap request from : checkForUpdates
The log level can be configured in the /etc/vmware/vpxa.cfg file. Just look for a section like the following. The possible levels are the same as those of VC logs: none, error, warning,info, verbose, or trivia, in an order from less to more detailed messages.
<log> <directory>/var/log/vmware/</directory> <name>hostd</name> <outputToConsole>false</outputToConsole> <level>verbose</level> </log>
After saving the configuration, you need to restart the hostd with the following command line:
service mgmt-vmware restart
It’s critical to synchronize the time of all the components involved, especially when you care about the sequences of actions and messages. You can configure NTP on ESX.