vRealize Infrastructure Navigator (VIN) is causing the vCenter Inventory service to crash (popup in the web client stating the Inventory service is not available).
This will allow you choose what time every day VIN will sync and stop the multi-day incremental syncs.
Follow this post on how to enable SSH and allow root to login. If not, you can type the commands in at the console.
See how many times per day the incremental syncs are happening.
cat /var/log/vadm/engine.log | grep Incremental
2016-10-16T22:17:44+00:00 info vadm-engine: [springTaskSched-10] c.v.v.s.i.InventoryServiceConnectorImpl – Incremental synchronization took 393ms
2016-10-16T22:19:44+00:00 info vadm-engine: [springTaskSched-14] c.v.v.s.i.InventoryServiceConnectorImpl – Incremental synchronization took 184ms
2016-10-16T22:48:45+00:00 info vadm-engine: [springTaskSched-2] c.v.v.s.i.InventoryServiceConnectorImpl – Incremental synchronization took 457ms
2016-10-16T22:53:45+00:00 info vadm-engine: [springTaskSched-8] c.v.v.s.i.InventoryServiceConnectorImpl – Incremental synchronization took 114ms
Run these 2 commands to see a history of how often (and duration) the full sync’s took.
cat /var/log/vadm/engine.log | grep “Cache synchronization took”
cd /var/log/vadm
zgrep -ia “Cache synchronization took” engine.log.*.bz2
2016-10-01T22:37:58+00:00 info vadm-engine: [springTaskSched-4] c.v.v.s.i.InventoryServiceConnectorImpl – Cache synchronization took 1342ms
2016-10-01T23:59:07+00:00 info vadm-engine: [springTaskSched-9] c.v.v.s.i.InventoryServiceConnectorImpl – Cache synchronization took 11429ms
2016-10-02T00:11:19+00:00 info vadm-engine: [springTaskSched-9] c.v.v.s.i.InventoryServiceConnectorImpl – Cache synchronization took 11508ms
2016-10-02T01:48:51+00:00 info vadm-engine: [springTaskSched-9] c.v.v.s.i.InventoryServiceConnectorImpl – Cache synchronization took 41218ms
2016-10-02T01:52:55+00:00 info vadm-engine: [springTaskSched-9] c.v.v.s.i.InventoryServiceConnectorImpl – Cache synchronization took 40791ms
2016-10-02T02:03:48+00:00 info vadm-engine: [springTaskSched-9] c.v.v.s.i.InventoryServiceConnectorImpl – Cache synchronization took 41224ms
2016-10-02T02:09:23+00:00 info vadm-engine: [springTaskSched-9] c.v.v.s.i.InventoryServiceConnectorImpl – Cache synchronization took 11404ms
2016-10-02T02:34:27+00:00 info vadm-engine: [springTaskSched-9] c.v.v.s.i.InventoryServiceConnectorImpl – Cache synchronization took 2643ms
Pick a time that you want it to sync every 24 hours.
Turn off syncing
curl http://localhost:8080/jolokia/exec/com.vmware.vadm:name=InventoryServiceConnector/setScheduledSyncIncrementallyEnabled/false
enable sync cache – default is 24 hours
curl http://localhost:8080/jolokia/exec/com.vmware.vadm:name=InventoryServiceConnector/setScheduledSyncCacheEnabled/true
date +%s will show poch tijme. Use http://www.epochconverter.com/ to convert to a human readable date timestamp
Confirm value = 86400 which is seconds. 86400/60= 1440/60= 24 hours
curl http://localhost:8080/jolokia/ -XPOST -d ‘{“type” : “exec”,”mbean” : “com.vmware.vadm:name=InventoryServiceConnector”,”operation” :”getSyncCacheFrequency()”,”arguments”:[]}’
This will show to start time in epoch
curl http://localhost:8080/jolokia/ -XPOST -d ‘{“type” : “exec”,”mbean” : “com.vmware.vadm:name=InventoryServiceConnector”,”operation” :”getLastStartTime()”,”arguments”:[]}’
Prove it is not Incrementally syncing. The last entry should be 24+ hours ago.
cat /var/log/vadm/engine.log | grep Incremental
Two or more days later run this command to show the perfect 24 hour cadence.
cat /var/log/vadm/engine.log | grep “Cache synchronization took”
