Its not a fix but as a workaround you could try extending the timeout period from 120 to 300 seconds, might give VCSA enough time to complete your query?
- Check the the webclient.properties file
- Take a copy of the file by running the command:
cp webclient.properties webclient.properties.bak
- Edit the webclient.properties file
- Change the line:
dataservice.timeoutSeconds = 120 to dataservice.timeoutSeconds = 300
- Restart the vCenter server for the change to take effect.
just for a test, try working with the HTML5 client for 6.5 (even if it's not complete ... and just a test)
let's see if the same operations (those allowed) generate the same error.
Would that also resolve the login time ? Because when a user logs in with AD credentials, it is taking long time to login.
Over HTML client, we aren't seeing errors but slowness is there. I am just not getting this as slowness was getting resolved after appliance reboot. But this time, after reboot issue seems to be persisting.
If the ticket is still open with support, try to see with them if a possible VCSA update could solve the slowness problem.
You can try the below things.
Check the dataservice.log if you are still seeing the "the query execution time out" issue. Paste the logs over here for further review.
Also, are there any third party plugins registered to the vCenter? If yes, then disable them and check if the issue persists.
Might be an idea to stay engaged with VMware Support, given that you may end up applying a "fix" from the advice you're given here which could be unsupported and therefore gets undone by a future patch or update.
That's a generic error which means a request for a property was sent and vCenter did not get any response in 120 seconds . Increasing the timeout will just delay the failures and not resolve it .
Do we have a VMware SR number ?
Also you have 100 Hosts . Is it exactly hundred or above 100 ? If above 100 ESXi ; then you should be a Medium Sized VCSA ( 8 vCPU's and 24GB RAM) .
Can you share the /etc/vmware/service-layout.mfx and also the vsphere_client_virgo.log from /var/log/vmware/vsphere-client/logs right after the issue is observed and mention the time .
I've got the same issue here.