Symptoms
- If you try to view Hardware Status information for an ESX in vCenter Server 4.0, you see the error:
The hardware monitoring service is not available - In the vws.log file of vCenter Server, you see errors similar to:
[2009-06-29 10:35:47,115 http-8443-1 ERROR 'com.vmware.vim.security.authenticate.servlets.AuthenticationServlet'] AuthorizeMgr not initialized.
[2009-06-29 10:35:47,302 http-8443-3 FATAL 'com.vmware.vim.query.servlets.QueryServlet'] Unable to find attribute QueryService
Note: The vws.log is in the same directory as the vpxd logs on the vCenter Server. The path to the logs is typically C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs. - If you log on directly to the ESX using the vSphere Client, Health Status information displays without errors
esx-hardware-status-fails
Resolution
This issue occurs if the keystorePass parameter in C:\Program Files\VMware\Infrastructure\tomcat\conf\server.xml is changed from the default testpassword topassword. Changing the keystorePass parameter from the default testpassword is not permitted. Also, the password used to generate the rui.pfx file must be testpassword.
To resolve this issue, you must restore the default settings.
To restore the default settings:
- Re-generate the rui.pfx file using the password testpassword.
Note: The rui.pfx file can be generated using OpenSSL with the existing rui.crt and rui.key files.
To generate the rui.pfx file with OpenSSL, run this command:
openssl.exe pkcs12 -export -in rui.crt -inkey rui.key -name rui -passout pass:testpassword -out rui.pfx
For more information, see Generating custom or default SSL certificates (1029944).
- Edit C:\Program Files\VMware\Infrastructure\tomcat\conf\server.xml and change thekeystorePass parameter from keystorePass="password" to keystorePass="testpassword".
- Restart the VMware VirtualCenter Management Webservices service on vCenter Server. For more information, seeStopping, starting, or restarting vCenter services (1003895).Based on VMware KB 1012325
