In this Vmware issue series, you will receive solution for maximum which is occurs on daily basis, \u00a0hope it will help.<\/p>\n
1st:<\/strong> \u00a0while trying to connect the\u00a0Virtual Infrastructure Web Access, it’s not opening, in that case simply restart the “Web Access” service from the command line<\/strong><\/p>\n service vmware-webaccess restart<\/p><\/blockquote>\n The above service will restart the Apache as well as Tomcat service which is used for “Virtual Infrastructure Web Access”.<\/p>\n 2nd:<\/strong> You are now able to connect the “VMware Infrastructure Client \/ vSphere Client” but you are receiving the following errors<\/strong><\/p>\n a: Not able to connect\u00a0ESXi\/ESX to VirtualCenter or vCenter Server<\/p>\n b: You are not able to access or connect any\u00a0ESXi\/ESX directly, the connection is timing out<\/p>\n To resolve the above issues, run the following command from the shell ( vmware ESX server) service mgmt-vmware restart<\/p><\/blockquote>\n If above command won’t resolve the issue, than run the following command in the sequence because it could be possible that\u00a0mgmt-vmware restart command does not restart hostd or script stuck.<\/p>\n Stop the restart service and if stuck than kill it using following commands<\/p>\n cd \/var\/run\/vmware<\/p><\/blockquote>\n Now check the vmware pid and watchdog pids<\/p>\n ls -l vmware-hostd.PID watchdog-hostd.PID<\/p><\/blockquote>\n Cat the files<\/p>\n cat vmware-hostd.PID<\/p>\n [root@admin]# cat vmware-hostd.PID kill -9 7802<\/p>\n rm -f vmware-hostd.PID<\/em>\u00a0watchdog-hostd.PID<\/em><\/p><\/blockquote>\n Now start the server once again<\/p>\n service mgmt-vmware start<\/p><\/blockquote>\n For ESXi, run the command:<\/p>\n \/etc\/init.d\/hostd start<\/p><\/blockquote>\n \u00a03rd: The\u00a0\/etc\/vmware\/hostd\/config.xml as well as\u00a0\/etc\/vmware\/hostd\/proxy.xml file is blank , how to recover it to resolve the\u00a0mgmt-vmware service restart issue, because empty files won’t allow to get\u00a0mgmt-vmware service restart.<\/strong><\/p>\n As\u00a0\/etc\/vmware\/hostd\/config.xml<\/strong> is blank , therefore need to restore it from the backup, there is no other way to recover it<\/p>\n For\u00a0\/etc\/vmware\/hostd\/proxy.xml<\/strong> file , simply restore it from the backup or copy the\u00a0\/etc\/vmware\/hostd\/proxy.xml<\/strong> file from another working host to resolve the issue.<\/p>\n You can check the server logs\u00a0hostd.log\u00a0when the\u00a0proxy.xml\u00a0file is empty, it will show you show the following errors<\/p>\n [2014-06-15 12:06:12.794\u00a0FFFCAE80 verbose ‘App’] Plugin 9 statically linked <\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":"
\n<\/strong><\/p>\n
\n7802[root@admin]#<\/p>\n
\n[2014-06-15 12:06:12.794\u00a0FFFCAE80 info ‘Proxysvc’] Proxy config filepath is \/etc\/vmware\/hostd\/proxy.xml
\n[2014-06-15 12:06:12.795\u00a0FFFCAE80 panic ‘App’] error: no element found
\n[2014-06-15 12:06:12.795\u00a0FFFCAE80 panic ‘App’] backtrace:
\n[00] rip 20d01c54
\n[01] rip 20b4304e
\n[02] rip 20b127a7<\/p><\/blockquote>\n