David, I know Wei Zhou committed a patch. It is in master and it should be in 4.3 as well.
On Tue, Feb 4, 2014 at 12:05 AM, David Bierce (JIRA) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/CLOUDSTACK-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889943#comment-13889943 > ] > > David Bierce edited comment on CLOUDSTACK-5890 at 2/3/14 11:04 PM: > ------------------------------------------------------------------- > > After upgrading from 4.1.1 to 4.2.1 I appear to be having this issue as well. > Which version was this fixed or is there still more information required? > Digging through the commit logs I don't see a patch submitted to this in > master, 4.3 or 4.2. > > > was (Author: dbierce): > After upgrading from 4.1.1 to 4.2.1 I appear to be having this issue as well. > Which version was this fixed or is there still more information required? > >> Error while collecting disk stats from vm >> ----------------------------------------- >> >> Key: CLOUDSTACK-5890 >> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5890 >> Project: CloudStack >> Issue Type: Bug >> Security Level: Public(Anyone can view this level - this is the >> default.) >> Components: Management Server, XenServer >> Affects Versions: 4.2.1, 4.3.0 >> Reporter: Daan Hoogland >> >> "Error while collecting disk stats from" is thrown a lot of times. >> 2014-01-16 00:00:56,006 WARN [xen.resource.CitrixResourceBase] >> (DirectAgent-137:null) Error while collecting disk stats from : >> You gave an invalid object reference. The object may have recently been >> deleted. The class parameter gives the type of reference given, and the >> handle parameter echoes the bad value given. >> at com.xensource.xenapi.Types.checkResponse(Types.java:209) >> at com.xensource.xenapi.Connection.dispatch(Connection.java:368) >> at >> com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909) >> at com.xensource.xenapi.VBDMetrics.getIoReadKbs(VBDMetrics.java:210) >> at >> com.cloud.hypervisor.xen.resource.CitrixResourceBase.getVmStats(CitrixResourceBase.java:2791) >> at >> com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2691) >> at >> com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:497) >> at >> com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59) >> at >> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186) >> at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) >> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) >> at java.util.concurrent.FutureTask.run(FutureTask.java:166) >> at >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) >> at >> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) >> at java.lang.Thread.run(Thread.java:679) >> xapi returns HANDLE_INVALID, after which the whole collection process for >> stops for this host as it is caught outside the loop. > > > > -- > This message was sent by Atlassian JIRA > (v6.1.5#6160) -- Daan
