Unable to Update Client0 to use new CPUS

[ChristianFredri]

During the VMmark Run Tiles stage, my run canceled out with the error:
Exception Found: Unable to Update Client0 to use new CPUS: CPUS: 8

No other detail, this came from the debug. Any help on resolving this?

[poovendiran]

Have the same issues when running VMmark 3.1 currently. Anyone managed to solve this issue?

[dmorse]

ChristianFredrickson​ I don't know why this never got answered, but the root cause from the .tar file you attached was this:

20180527-21:42:25 Info  Error: machName = Client0 : Invalid Trust Level (3)

20180527-21:42:25 Info  STAF Trust Level incorrect for the following machines:1 machines [VM reboot may be required] : Client0

20180527-21:42:25 Info  Service: Starting VMmark3 Emailer

If this is still an issue, please let me know

[dmorse]

Can you start a new thread and attach a screenshot of the issue you're seeing please?

[poovendiran]

This is the error message. We are using the latest Cascade Lake CPUs with a 2-node cluster. We have updated the VMware tools and virtual hardware version but doesn't solve the problem.

[jpschnee]

Poovendiran,

I suspect the issue is you have configured the benchmark to attempt Deploy operations against your client(s) instead of DeployVMs.  Please upload your VMmark3.properties file so we can help review.

[poovendiran]

Hi,

Please find the file from our 3.0 deployment attached (we deleted the 3.1 deployment due to the issue). Hope you can help. Noticed from a couple of the properties files loaded in the forum, the Client0 info is not specified under the Deploy/DeployVMinfo section, whereas it is there in our file. So, should Client0 be defined there or not?

[dmorse]

Please find the file from our 3.0 deployment attached (we deleted the 3.1 deployment due to the issue). Hope you can help. Noticed from a couple of the properties files loaded in the forum, the Client0 info is not specified under the Deploy/DeployVMinfo section, whereas it is there in our file. So, should Client0 be defined there or not?

No, Client0 should not be in the DeployVMinfo line.  Per the properties file you attached, I would suggest setting Deploy/DeployVMinfo as such:

Deploy/DeployVMinfo = DeployVM0:192.168.42.245

Then, add this line to your /etc/hosts file on your primeclient VM:

192.168.42.245 DeployVM0

Hope that helps!

[dmorse]

If you have already run the benchmark with Client0 in the DeployVMinfo line, your Client0 VM has likely been overwritten by the template, which is why you get the "Unable to update Client0 to use new CPUS".

If that is the case, I would recommend deleting the tile0 VMs (all VMs ending in zero) and recreating tile0 after the DeployVMinfo has been corrected.

[poovendiran]

Thanks David. This solved the problem.