ESX3.5: Configuration Issue detected, new strange error

[kri-2]

Could an admin please move this thread to ESX3.5 Forum?

Hi,

Configuration Issue: Issue detected on hostxyz. Virtual machine creation may fail because agent is unable to retrieve vm creation.

a few weeks ago we got this error the first time for one of our hosts. After restarting the services vpxa and mgmt the host worked fine again and we hoped to not see it again. But the last days we realised the error another two times, and today we have three more hosts in one farm showing this strange errormessage. So it seems to be/get a bigger problem...

The affectet hosts show the same behaviour:

-yellow exclamation mark

-No VMotion anymore (error: the session is not authenticated)

-No performance data

-the LUNs are not visible (in VC)

-No VM actions possible (power on/off,...)

...so there seems to be no way for the VC to query anything from the hosts or talk to him.

The good thing: all VMs are up and running

I could not find any errors in the logfiles that tell me more.

Is there anybody who has the same strange error and knows where it could come from?

Chris

[Texiwill]

Hello,

Moved to ESX 3.5 forum.

From the CLI run:

service mgmt-vmware restart

to fix this problem. Basically hostd is out of sync with vCenter.

Best regards,
Edward L. Haletky
VMware Communities User Moderator
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast

[kri-2]

Hi Texiwill,

thanks, but what do you mean with out of sync. Is it a time based problem?

And how do we solve this for the future?

Chris

[allb18c]

We have the same error message here. A restart of the management service did not resolve the problem.

Any other recommendations? I want to remove/add the host back however I am wary that it will work since we have running production on it.

Thanks

[kri-2]

You just need to restart the vmware-vpxa service.

/etc/init.d/vmware-vpxa restart

This can be done at any time, the virtual machines are not affected by this command.

[allb18c]

Resolved - thanks much.:D

[Matt_B1]

Restarting vmware-vpxa worked for me also. However, as noted earlier in this thread, why does this warning ever occur? I would like to prevent this from happening on any of my ESX hosts to ensure optimal functionality at all times.

[sbeaver]

Dont we all!! Sometimes crap just happens and now you know how to resolve. Things like this can happen. It should not happen alot

Steve Beaver

VMware Communities User Moderator

VMware vExpert 2009

====

Co-Author of "VMware ESX Essentials in the Virtual Data Center"

(ISBN:1420070274) from Auerbach

Come check out my blog: www.theVirtualBlackHole.com

Come follow me on twitter

*Virtualization is a journey, not a project.*