Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 17 Jan 2014 09:43:20 +0000 (UTC)
From: "Daan Hoogland (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12689404.1389915954208.22864.1389951800514@arcas>
In-Reply-To: <JIRA.12689404.1389915954208@arcas>
References: <JIRA.12689404.1389915954208@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-5890) Error while collecting disk
 stats from vm
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874603#comment-13874603 ] 

Daan Hoogland commented on CLOUDSTACK-5890:
-------------------------------------------

It seems to happen specifically on VBDs that have a kps read count of
'unknown'. But it happens a lot so I don;t know if that is the only
situation.


> 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)