prashant kumar mishra created CLOUDSTACK-5834:
-------------------------------------------------

             Summary: [upgrade]Error while collecting disk stats from : You 
gave an invalid object reference.  The object may have recently been deleted
                 Key: CLOUDSTACK-5834
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5834
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server, XenServer
    Affects Versions: 4.3.0
            Reporter: prashant kumar mishra
             Fix For: 4.3.0


Steps 
======
1-prepare ACS 4.2 setup with xen6.2 host
2-upgrade CS to 4.3 and upgrade xen 6.2 to xen6.2sp1

After upgrade i am seeing error message in log whenever VmStatsCollector is 
running.

Logs
======

2014-01-08 13:15:08,182 DEBUG [c.c.s.StatsCollector] 
(StatsCollector-2:ctx-aa75b506) VmStatsCollector is running...
2014-01-08 13:15:08,207 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-141:ctx-74d0d04a) Seq 1-498139202: Executing request
2014-01-08 13:15:08,358 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-141:ctx-74d0d04a) Vm cpu utilization 0.0
2014-01-08 13:15:08,359 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-141:ctx-74d0d04a) Vm cpu utilization 0.00453125
2014-01-08 13:15:08,369 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-141:ctx-74d0d04a) 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:2784)
        at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2684)
        at 
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:493)
        at 
com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59)
        at 
com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:106)
        at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
        at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
        at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
        at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
        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)
2014-01-08 13:15:08,371 DEBUG [c.c.a.m.DirectAgentAttache] 
(DirectAgent-141:ctx-74d0d04a) Seq 1-498139202: Response Received:








--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to