The service referenced above is on the ESX host.
You can try restarting it:
# service mgmt-vmware restart[/code]
It seems that sometimes the VC server has problems updating agents on hosts. Restarting the existing agent has been reported to solve this.
Or you can install the agent service manually. There are many (recent) examples of this on the forums.
Message was edited by:
hicksj
fixed service typo
Am I starting the VC or ESX host? Thanks. Restrating VC did not resolve this.
The service referenced above is on the ESX host.
\
service mgmt-vmware restart
doing this worked for me
For me too \*sic*. But I'd like to add that VM operation is \_not_ disturbed by this procedure.
restarting the mamagement agents on the esx hosts worked for me as well !!
Just had this issue on a few servers after installing patch 2 for VirtualCenter - fixed it perfect.
I have this problem and this solution works fine for me. But all virtual machines in the ESX servers has rebooted after the execution of this command.
This is normal?
\
service mgmt-vmware restart
This worked for me as well, however I had to also do:
\# /etc/init.d/vmware-vpxa start
as that service was stopped and it wouldn't be added to VirtualCenter without it...
hi,
i know its relatively old post but the method is still not working for me after trying all the above said its still gives the same error..
can you help me out with the work around.
regards,
Siddharth.
I also had the same issue. The only thing that seemed to work was killing multiple sessions from the VIC for the same user. Once that was done my Host was successfuly added back to my cluster.