VMware Cloud Community
si-sys
Contributor
Contributor

Unable to apply DRS resource settings

Hi,

I've got that message on one of my ESX 3.5 hosts :

"Unable to apply DRS resource settings on host 'xxx' in xxx' (Reason: A general system error occured: Invalid Fault)."

It appears about 2-3 times a day in the event log. That host has nothing different from others. It's in a DRS + HA cluster.

Any idea ?

Reply
0 Kudos
9 Replies
si-sys
Contributor
Contributor

Additional informations : I tried to put the host in maintenance mode in order to reboot it and there is a problem migrating one VM :

"Operation failed since another task is in progress."

It's a Debian VM, which hasn't have problems till now.

Maybe that thread should me moved to a better category...

Reply
0 Kudos
si-sys
Contributor
Contributor

Sorry for the noise folks.

A simple "service mgmt-vmware restart" solved the problem...

Reply
0 Kudos
mandg
Contributor
Contributor

Hi si-sys,

I now have the same issue on one of my hosts after upgrading to VC 2.5 update 2, and ESX 3.5. Does the restart service command you reference cause any disruption to production? Meaning, is it safe to run while the host has active guests?

Thanks.

Reply
0 Kudos
MHAV
Hot Shot
Hot Shot

Hi,

what Update of ESX 3.5 you are using? ESX 3.5 U1 has this problem.

To resolve it you have to update to ESX 3.5 U2.

Regards

Michael

Regards Michael Haverbeck Check out my blog www.the-virtualizer.com
Reply
0 Kudos
mandg
Contributor
Contributor

I'm running ESX 3.5 - no U's (yet)

Reply
0 Kudos
sg222
Contributor
Contributor

We had the same problem here. We updated our servers from build 82663 (update 1) to 130756 (update 3) and after completion of update on our second host, we got this error message.

restart of mgmt-vmware service solved the problem for us. We just had to reconfigure HA and drs worked fine again.

Reply
0 Kudos
mspencer3
Contributor
Contributor

Hi All,

We had this same exact issue and found that after migrating to the new VCenter 2.5 to support our ESX3.5 servers one of the ESX3.02 servers that was migrated did not pick up the licenses from the license servers...

To resolve this we removed the host from the VCluster (no VM or host downtime needed)

Disconnected, Removed.

We connected directly to the host and set the license to unlicensed and then back to licensed from the same license server.

Readded the host to the folder containing the original cluster.. Note we did not add it directly to the cluster

Verified that VCenter saw the host as licensed

Added the host to the VMCluster

All was resolved.

hope this helps...

Mark

Reply
0 Kudos
waldronmct
Contributor
Contributor

I know this is an incredibly late answer, but this KB has resolved this issue for me:

All I had to do was the first suggestion.

Dave

Reply
0 Kudos
JDMils
Enthusiast
Enthusiast

When upgrading, VMware Tools gets upgraded as well and sometimes it just gets stuck in the "upgrading" step. Right-click each virtual and select "Guest | End VMware Tools Install".

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102602...

| +-- JDMils | +-- ESXi 4.1.0, clustered hosts, HA, DRS & VMotion enabled. |
Reply
0 Kudos