Hallo, so we still have the problem that the inventory collection takes 30 minutes while it should take no more than 2 minutes. The inventory consists of one Cluster, two ESX servers and 20 VMs. ...
See more...
Hallo, so we still have the problem that the inventory collection takes 30 minutes while it should take no more than 2 minutes. The inventory consists of one Cluster, two ESX servers and 20 VMs. We did a man in the middle attack between the vCenter and the agent and looked at the traffic. What we can see that the inventory collection consts of one long TCP connection, the agent issues soap calls and the calls are immediatly ansswer, but sometimes the agent waits upto _1 minute_ to issue the next soap call. I assume that this is the symptom. Also when I compare the throughput flow graph of a installation that works with the one that does not, I can see that the one that does not work bursts and than sleeps while the one that works has a constant flow of throughput. We tried to reinstall the vcac server with the same image as the environment where it works, but still have the problem. We also added the hosts entries to the vcac server, no change. We tried to use sysinternals process explorer to monitor the agent, but the only thing we can see here that the delta between writing to the .config file and thread exit is 6 seconds instead of a fraction of a second. So next we try to install vcac without joining the active directory and reinstall a new vcenter and see if the poblem persists. The debug log shows nothing because there is only logged when the inventory location starts, finishes and is propagated to the vcac server. Cheers, Thomas We opened a SR: 13330063105