cmorris05
Contributor
Contributor

Unable to apply DRS Resource Settings... Invalid Fault

I am getting an error on my ESX server after I ran the latest set of updates, I am not sure what kind of effect it is having my cluster yet, however the error is "Unable to apply DRS resource settings on host (hostname) in (Datacenter Name) (Reason: A general system error occurred: Invalid Fault.) This can significantly reduce the effectiveness of DRS.

Has anyone seen this error?

0 Kudos
23 Replies
chevy372
Contributor
Contributor

Out of our 7 server farm, so far 1 of them has come up with this error after upgrading.

0 Kudos
cmorris05
Contributor
Contributor

I have opened a case with VMware on this issue, but we have found that something has happend with the way it is handling resource pools, if you compare your pools.xml file between your server, you may see a difference.

I did anyways.

0 Kudos
chevy372
Contributor
Contributor

I reconfigured mine for HA, and it went away on its own after that.

0 Kudos
cmorris05
Contributor
Contributor

I tried that and it seemed to work for about 10 minutes and the error came back.

0 Kudos
Erik_Zandboer
Expert
Expert

Hi,

Saw this problem today on a three-host cluster which was just upgraded to ESX 3.5u2 (+ VC 2.5u3). One of the hosts came with this error/warning. After logging into the host directly, things became more clear. It was trying to updat child resource pools, but these tasks failed because "another task was in progress". Sure thing, a very big snapshot was being removed from one of the VMs on that hosts. I figured:

--> VC thinks no tasks are in progress because the remove snapshot action took too long and timed out on VC;

-->The ESX host itself though,was still going strong on removing this snapshot;

-->VC (read: DRS) was trying to update the child resource pools since it thought no task was in progress (and needed to so DRS would remain satisfied);

-->The tasks of updating the child resource pools on the host by DRS then failed for the reason above;

-->VC does not know what is going on, and reports the error in the subject of this thread.

Maybe in your case something equal is going on. After the host finally got rid of the snapshot (19GB), I disabled DRS on the cluster (no resource pools where defined so that was easilly done). After that the error disappeared. Activating DRS once again, and was well... Hope this helps in solving your problem!

Visit my blog at http://www.vmdamentals.com
0 Kudos
prime
Contributor
Contributor

I am getting an error on my ESX server after I ran the latest set of updates, I am not sure what kind of effect it is having my cluster yet, however the error is "Unable to apply DRS resource settings on host (hostname) in (Datacenter Name) (Reason: A general system error occurred: Invalid Fault.) This can significantly reduce the effectiveness of DRS.

I've seen this before. The fix for me was to make sure that the VMTools was unmounted from every host. I had two hosts that still had the VMTools image mounted. When I unmounted them then the error went away.

0 Kudos
LarsLiljeroth
Expert
Expert

Just had this issue.

It was the guests that had a CD set to Deveice type "client device" When i removed those. the error disapeared.


Best regards

Lars Liljeroth

// Lars Liljeroth -------------- *If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
0 Kudos
georgewc3
Contributor
Contributor

I disabled DRS on the cluster (no resource pools where defined so that was easilly done). After that the error disappeared. Activating DRS once again, and was well... Hope this helps in solving your problem!

The above worked for me. Although it was irritating.

George Warren International Project Engineer FUJIFILM Medical Systems USA, Inc.
0 Kudos
pdarcysgi
Contributor
Contributor

Hi Erik Zandboer

I also had the exact same issue as you when I was removing a large snapshot. My question once I have disabled DRS and enabled it again does that resolve the issue or does it come up again? what is changed by just disabling DRS and re-enabling it again?

Thank

P

0 Kudos
pdarcysgi
Contributor
Contributor

Hi Erik Zandboer

I also had the exact same issue as you when I was removing a large snapshot. My question once I have disabled DRS and enabled it again does that resolve the issue or does it come up again? what is changed by just disabling DRS and re-enabling it again?

Thank

P

0 Kudos
k_j
Contributor
Contributor

I solved this problem by removing a buggy host from a cluster, connecting VI client to the removed host and deleting all resource pools.

At last I have to add the host back to the cluster.

0 Kudos
loewenholz
Contributor
Contributor

Update VMWare Tools!

One Server hang on VMWare Tool installation and after reboot this server it fixed my Problem.

0 Kudos
mnasir
Enthusiast
Enthusiast

I am having the same issue after upgarding to 3.5U4, I am currently on the phone with VMware. I will post any solution I get from vmware.

0 Kudos
mnasir
Enthusiast
Enthusiast

I got the same error after upgrading my esx server 3.5U4, please use the command below to resolve the issue:

1. Disconnect your host from the cluster and create an SSH session to that host

2. use su - to become root

rpm -qa | egrep -i '(vpx|lgto|aam)'; ls /tmp/vmware-root

rpm -e `rpm -qa | egrep -i '(vpx|lgto|aam)'`; rm -rf /etc/vmware/hostd/pools.xml; rm -rf /etc/vmware/license.cfg; userdel vpxuser;service mgmt-vmware restart

tail -f /var/log/vmware/hostd.log | grep BEGIN

Wait for the BEGIN to show up on your console

Reconnect the host to the cluster.

Thanks - Please consider giving points, if you think this post was helpful.

0 Kudos
Guy_Chapman
Contributor
Contributor

This worked for me (on 3.5u4). I am guessing that the effect is similar to the steps listed at the foot of the thread, but the GUI method is a little easier.

So: Maintenance mode, disconnect and remove from cluster, connect VI client direct to host, remove resource pools, reconnect to cluster. Quick and dirty, does the job.

0 Kudos
Munster
Contributor
Contributor

Hi Guys (n Gals)

I had the exact same problem here and found that before the 'fix' was applied I confirmed ALL the VMs on the problem hosts needed to have the tools installed and configured properly. I had two hosts (out of 10) with this issue and confirmed that 2 windows VMs had tools that were old and non-responsive - rebooted them and installed the tools and the errors went away.

Regards

Munster

0 Kudos
dylanswift
Contributor
Contributor

unmounting the VMTools image worked for me (on 1 host). Cluster recovered itself without my intervention.

Dylan

0 Kudos
paulmack
Enthusiast
Enthusiast

0 Kudos
jmascone
Contributor
Contributor

Unmounting the VMTools image on affected VMs (right-click VM, Click End VMWare Tools Install) has worked for me in two different situations (different hosts on different clusters)...The KB article, imho, might be a bit of overkill...

0 Kudos