wade001
Contributor
Contributor

usage meter failed collections

I have had usage meter installed for a few months starting with version 2.1 after a month of running fine i began frequently receving failed collection notices, upgrading to version 2.2 seemed to help for a while but after a week i began to recieve these notification once again... any ideas...

A collection from x.x.x.x, begun at 2011-10-27 16:10:53, failed at 2011-10-27 16:11:15.

Usage Meter will abandon collecting from this vCenter Server until the next collection cycle.

java.net.SocketException: Connection reset

org.apache.axis.AxisFault.makeFault(AxisFault.java:101)

org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)

org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)

org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)

org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)

org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)

org.apache.axis.client.Call.invokeEngine(Call.java:2784)

org.apache.axis.client.Call.invoke(Call.java:2767)

org.apache.axis.client.Call.invoke(Call.java:2443)

org.apache.axis.client.Call.invoke(Call.java:2366)

org.apache.axis.client.Call.invoke(Call.java:1812)

com.vmware.vim25.VimBindingStub.login(VimBindingStub.java:44092)

com.vmware.cloud.usgmtr.collect.vc.VCenterCollector.logIn(VCenterCollector.scala:48)

com.vmware.cloud.usgmtr.collect.VcDataHandler.getFromVc(VcDataHandler.scala:75)

com.vmware.cloud.usgmtr.collect.VcDataHandler.collectSamples(VcDataHandler.scala:30)

com.vmware.cloud.usgmtr.collect.Collector$.collectAndSaveSamples(Collector.scala:91)

com.vmware.cloud.usgmtr.collect.Collector$.collectAndSaveSamples(Collector.scala:131)

com.vmware.cloud.usgmtr.collect.Collector$.collectAndSaveSamples(Collector.scala:131)

com.vmware.cloud.usgmtr.collect.Collector$$anonfun$com$vmware$cloud$usgmtr$collect$Collector$$collectAll$1.apply(Collector.scala:70)

com.vmware.cloud.usgmtr.collect.Collector$$anonfun$com$vmware$cloud$usgmtr$collect$Collector$$collectAll$1.apply(Collector.scala:70)

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)

Tags (2)
0 Kudos
2 Replies
IamTHEvilONE
Immortal
Immortal

wade,

Is there any form of firewall between the Usage Meter instance and the vcenter it's referring to?  Especially if it terminates TCP connections after being idle for some time.

Connection Reset is much akin to the path being forced closed.

Would you be able to post the logs from Usage Meter on here (scrubbing if required).

Best Regards,

Jon Hemming

0 Kudos
wade001
Contributor
Contributor

thanks there is not a FW issue between the appliance and the vCenter. Most of the collection pools are completing ok it appears to sporaticly fail on some polling internvals.  Attached is the log.

0 Kudos