agallagh42
Contributor
Contributor

Usage Meter 2.3 collection error "key not found: host"

I'm having a problem with vCloud Usage Meter 2.3.  Everything was fine with 2.1  and 2.2.  We have 5 different vCenter servers that we are collecting from, and  only this one is a problem.  It seems to be failing on a specific  host.

All hosts in this environment are running ESXi 4.1 U2, and vCenter  is also at 4.1 U2.  The only exceptions are two hosts that are still running ESX  3.5. "host-748" is one of the 3.5 hosts.  It is currently connected properly to  vCenter and appears healthy.

---

A collection from 192.168.x.x, begun at 2012-04-03 15:10:04, failed at  2012-04-03 15:10:07.
Usage Meter will wait 300 seconds and retry one more  time.
java.util.NoSuchElementException: key not found:  host-748

scala.collection.MapLike$class.default(MapLike.scala:224)
scala.collection.immutable.HashMap.default(HashMap.scala:36)
scala.collection.MapLike$class.apply(MapLike.scala:135)
scala.collection.immutable.HashMap.apply(HashMap.scala:36)
com.vmware.cloud.usgmtr.collect.Vms$anonfun$save$1$anonfun$apply$mcV$sp$2.apply(Vms.scala:46)
com.vmware.cloud.usgmtr.collect.Vms$anonfun$save$1$anonfun$apply$mcV$sp$2.apply(Vms.scala:15)
scala.collection.TraversableLike$WithFilter$anonfun$foreach$1.apply(TraversableLike.scala:704)
scala.collection.LinearSeqOptimized$class.foreach(LinearSeqOptimized.scala:59)
scala.collection.immutable.List.foreach(List.scala:45)
scala.collection.TraversableLike$WithFilter.foreach(TraversableLike.scala:703)
com.vmware.cloud.usgmtr.collect.Vms$anonfun$save$1.apply$mcV$sp(Vms.scala:15)
com.vmware.cloud.usgmtr.collect.Vms$anonfun$save$1.apply(Vms.scala:12)
com.vmware.cloud.usgmtr.collect.Vms$anonfun$save$1.apply(Vms.scala:12)
org.squeryl.dsl.QueryDsl$class.inTransaction(QueryDsl.scala:102)
org.squeryl.PrimitiveTypeMode$.inTransaction(PrimitiveTypeMode.scala:40)
com.vmware.cloud.usgmtr.collect.Vms$.save(Vms.scala:12)
com.vmware.cloud.usgmtr.collect.Collector$anonfun$saveResults$1.apply(Collector.scala:116)
com.vmware.cloud.usgmtr.collect.Collector$anonfun$saveResults$1.apply(Collector.scala:111)
org.squeryl.dsl.QueryDsl$class._using(QueryDsl.scala:46)
org.squeryl.dsl.QueryDsl$class._executeTransactionWithin(QueryDsl.scala:114)
org.squeryl.dsl.QueryDsl$class.transaction(QueryDsl.scala:84)
org.squeryl.PrimitiveTypeMode$.transaction(PrimitiveTypeMode.scala:40)
com.vmware.cloud.usgmtr.collect.Collector$.saveResults(Collector.scala:111)
com.vmware.cloud.usgmtr.collect.Collector$.collectAndSaveSamples(Collector.scala:73)
com.vmware.cloud.usgmtr.collect.Collector$.collectAndSaveSamples(Collector.scala:99)
com.vmware.cloud.usgmtr.collect.Collector$anonfun$collectAll$2$anonfun$apply$1.apply$mcV$sp(Collector.scala:30)
com.vmware.cloud.usgmtr.collect.Collector$anonfun$collectAll$2$anonfun$apply$1.apply(Collector.scala:29)
com.vmware.cloud.usgmtr.collect.Collector$anonfun$collectAll$2$anonfun$apply$1.apply(Collector.scala:29)
org.squeryl.dsl.QueryDsl$class._using(QueryDsl.scala:46)
org.squeryl.dsl.QueryDsl$class._executeTransactionWithin(QueryDsl.scala:114)
org.squeryl.dsl.QueryDsl$class.transaction(QueryDsl.scala:78)
org.squeryl.PrimitiveTypeMode$.transaction(PrimitiveTypeMode.scala:40)
com.vmware.cloud.usgmtr.collect.Collector$anonfun$collectAll$2.apply(Collector.scala:28)
com.vmware.cloud.usgmtr.collect.Collector$anonfun$collectAll$2.apply(Collector.scala:28)
com.vmware.cloud.usgmtr.commons.Parallelizer$anonfun$2$anon$1.call(Parallelizer.scala:18)
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
java.util.concurrent.FutureTask.run(FutureTask.java:138)
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
java.lang.Thread.run(Thread.java:662)

Labels (1)
0 Kudos
4 Replies
Navpreet2011101
Contributor
Contributor

This issue has been reported to VMware. It is happening because ESX 3.5 hosts uses license server for their licensing.

It is expected to fixed in next release of vCloud Usage Meter.

0 Kudos
Socrates82
Enthusiast
Enthusiast

am having the same issue, does any one know if this is solved or yet, and what version should we use??

0 Kudos
admin
Immortal
Immortal

This was tested in version 3.0 which is now GA and is resolved.  Please download the update file to version 3.0 if you can run an in place upgrade.

Note that you should run a snapshot of the usage meter appliance before the upgrade in case of error and remove your email password fof SMTP server if you are using a password since we changed the encryption functionality when storing passwords.  The password should be entered again in post upgrade.

0 Kudos
Socrates82
Enthusiast
Enthusiast

Actually I have upgraded to 2.3.2 and the issue is solved; all the collections are ok now. Thanks for your help

0 Kudos