Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A26861066B for ; Thu, 16 Jan 2014 22:17:06 +0000 (UTC) Received: (qmail 55073 invoked by uid 500); 16 Jan 2014 22:17:04 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 55032 invoked by uid 500); 16 Jan 2014 22:17:03 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 55024 invoked by uid 99); 16 Jan 2014 22:17:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jan 2014 22:17:03 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: unknown (athena.apache.org: error in processing during lookup of pdion@cloudops.com) Received: from [209.85.217.169] (HELO mail-lb0-f169.google.com) (209.85.217.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jan 2014 22:16:58 +0000 Received: by mail-lb0-f169.google.com with SMTP id q8so2459783lbi.0 for ; Thu, 16 Jan 2014 14:16:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=lBq+NhBZnqHyOP+LE4aw0OUNy9DY8ZudpBDWiS9dXfo=; b=K0ifXEEGgk8VySWqOmWTV3BoQ9oIL1VxNOyQNRqVhDCuPfc5dUCjWlWW960gEaR0RT Kugmwx2DYJiH79VCvinUYGpmNoKk2GXopOx6RQ6R7ynGoJ1lC7+StC3vtyVEvTfrC9XL /Q2C6iMvUyFPixQxmhPc8t8ed451aFUpPyU/+QjTGv0HZMqpa+SU15eVLaMSuermOFrz sapAcbs2KY9lJEkRah0NgFYjIqYmyUftWjtgr4B2PzmOl1Q1RMX8E8FLqF2FVkPbS/wW rKCIf87of05OFxo0M/udHF60mTDeZKhPFFSTIqYnPcpY9gri86VLcXMVkFPVS0V/M61y Jwug== X-Gm-Message-State: ALoCoQkyDzyU5qbBKKwAcWvdaLO1IFn2Na/wPKBWIu9ewFKT3oGRUHfxEbS9XccmpI1YlvCqKGXc MIME-Version: 1.0 X-Received: by 10.112.139.72 with SMTP id qw8mr6155868lbb.16.1389910596067; Thu, 16 Jan 2014 14:16:36 -0800 (PST) Received: by 10.114.23.131 with HTTP; Thu, 16 Jan 2014 14:16:35 -0800 (PST) Date: Thu, 16 Jan 2014 17:16:35 -0500 Message-ID: Subject: Issues after upgrading CS from 4.1 to 4.2.1 managing XenServer 6.0.2 clusters From: Pierre-Luc Dion To: users@cloudstack.apache.org Content-Type: multipart/mixed; boundary=089e0112c1ba5977d804f01dc7fa X-Virus-Checked: Checked by ClamAV on apache.org --089e0112c1ba5977d804f01dc7fa Content-Type: multipart/alternative; boundary=089e0112c1ba5977d404f01dc7f8 --089e0112c1ba5977d404f01dc7f8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable We've upgrade our Cloudstack environment from 4.1 to 4.2.1, it is currently managing XenServer 6.0.2 clusters. 1. Since we have upgraded to 4.2.1 we noticed that Secondary Storage Name have been rename and we now see UUID's of SS. 2. On one cluster that is using local-Storage and Shared Storage we have removed on host from the XenServer Pool, since then, this error keep repeating in the management-server.log: 2014-01-16 17:01:17,898 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-437:null) Seq 1-590413869: Response Received: 2014-01-16 17:01:17,898 DEBUG [agent.transport.Request] (StatsCollector-2:null) Seq 1-590413869: Received: { Ans: , MgmtId: 152067623530867, via: 1, Ver: v1, Flags: 10, { GetVmStatsAnswer } } 2014-01-16 17:01:17,949 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-73:null) Seq 2-1599340596: Executing request 2014-01-16 17:01:18,191 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-320:null) Ping from 69 2014-01-16 17:01:18,369 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utilization 0.006406249999999999 2014-01-16 17:01:18,369 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utilization 12.9175 2014-01-16 17:01:18,369 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utilization 24.08 2014-01-16 17:01:18,369 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utilization 0.29500000000000004 2014-01-16 17:01:18,369 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utilization 23.8075 2014-01-16 17:01:18,370 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utilization 10.09875 2014-01-16 17:01:18,370 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utilization 0.29828125 2014-01-16 17:01:18,370 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utilization 2.6500000000000004 2014-01-16 17:01:18,370 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utilization 0.8375 2014-01-16 17:01:18,507 WARN [xen.resource.CitrixResourceBase] (DirectAgent-73: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$XenServerConnecti= on.dispatch(XenServerConnectionPool.java:909) at com.xensource.xenapi.VBDMetrics.getIoReadKbs(VBDMetrics.java:210) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.getVmStats(CitrixResou= rceBase.java:2791) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResource= Base.java:2691) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixR= esourceBase.java:497) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenSer= ver56Resource.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(Sc= heduledThreadPoolExecutor.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1= 146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:= 615) at java.lang.Thread.run(Thread.java:701) 2014-01-16 17:01:18,509 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-73:null) Seq 2-1599340596: Response Received: Also, Because we were planning to upgrade the pool using Local-Storage we start moving VM into another Primary Storage using regular procedure of turning off Instances, and moving them as Admin account. this keep failing but also delete Instance DISK which result of having data lost. Now, we can't see our hosts list and System VM list from the Infrastructure tab (see attachements), we only see ERROR. here is the apilog.log when trying to show hosts: 2014-01-16 17:13:35,337 INFO [cloud.api.ApiServer] (catalina-exec-18:null) (userId=3D2 accountId=3D2 sessionId=3D4F907F8E77BE76ADF46BB4FBE6B23BC0) 172.24.0.20 -- GET command=3DlistHosts&response=3Djson&sessionkey=3DtPdf1uSuogiM1ubmRFuPuFV%2F= LzM%3D&page=3D1&pageSize=3D20&type=3Drouting&listAll=3Dtrue&_=3D13899104152= 01 530 null is their any other logs to look at to understands what's broken because the upper stacktrace is clueless for me and their is no errors in the management-server.log when trying to display hosts. Regards, Pierre-Luc Dion Architecte de Solution Cloud | Cloud Solutions Architect 514-447-3456, 1101 - - - *CloudOps*420 rue Guy Montr=E9al QC H3J 1S6 www.cloudops.com @CloudOps_ --089e0112c1ba5977d404f01dc7f8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
We've upgrade our Cloudstack environment from 4.1 to 4= .2.1, it is currently managing XenServer 6.0.2 clusters.=A0

<= div>1. Since we have upgraded to 4.2.1 we noticed that Secondary Storage Na= me have been rename and we now see UUID's of SS.
2. On one cluster that is using local-Storage and Shared Storage we ha= ve removed on host from the XenServer Pool, since then, =A0this error keep = repeating in the management-server.log:

2014-01-16 17:01:17,898 DEBUG [agent.manager.DirectAgentAttache] (DirectA= gent-437:null) Seq 1-590413869: Response Received:
2014-01-16 17:01:17,898 DEBUG [agent.transport.Request] (StatsCollector-2:n= ull) Seq 1-590413869: Received: =A0{ Ans: , MgmtId: 152067623530867, via: 1= , Ver: v1, Flags: 10, { GetVmStatsAnswer } }
2014-01-16 17:01:17,949 DEB= UG [agent.manager.DirectAgentAttache] (DirectAgent-73:null) Seq 2-159934059= 6: Executing request
2014-01-16 17:01:18,191 DEBUG [agent.manager.DirectAgentAttache] (DirectAge= nt-320:null) Ping from 69
2014-01-16 17:01:18,369 DEBUG [xen.resource.Ci= trixResourceBase] (DirectAgent-73:null) Vm cpu utilization 0.00640624999999= 9999
2014-01-16 17:01:18,369 DEBUG [xen.resource.CitrixResourceBase] (DirectAgen= t-73:null) Vm cpu utilization 12.9175
2014-01-16 17:01:18,369 DEBUG [xen= .resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utilization 24.0= 8
2014-01-16 17:01:18,369 DEBUG [xen.resource.CitrixResourceBase] (DirectAgen= t-73:null) Vm cpu utilization 0.29500000000000004
2014-01-16 17:01:18,36= 9 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu util= ization 23.8075
2014-01-16 17:01:18,370 DEBUG [xen.resource.CitrixResourceBase] (DirectAgen= t-73:null) Vm cpu utilization 10.09875
2014-01-16 17:01:18,370 DEBUG [xe= n.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utilization 0.2= 9828125
2014-01-16 17:01:18,370 DEBUG [xen.resource.CitrixResourceBase] (DirectAgen= t-73:null) Vm cpu utilization 2.6500000000000004
2014-01-16 17:01:18,370= DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-73:null) Vm cpu utili= zation 0.8375
2014-01-16 17:01:18,507 WARN =A0[xen.resource.CitrixResourceBase] (DirectAg= ent-73:null) Error while collecting disk stats from :
You gave an inval= id object reference. =A0The object may have recently been deleted. =A0The c= lass 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.xenso= urce.xenapi.Connection.dispatch(Connection.java:368)
at com.cloud.hyperv= isor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenS= erverConnectionPool.java:909)
at com.xensource.xenapi.VBDMetrics.getIoReadKbs(VBDMetrics.java:210)
at = com.cloud.hypervisor.xen.resource.CitrixResourceBase.getVmStats(CitrixResou= rceBase.java:2791)
at com.cloud.hypervisor.xen.resource.CitrixResourceBa= se.execute(CitrixResourceBase.java:2691)
at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(Citr= ixResourceBase.java:497)
at com.cloud.hypervisor.xen.resource.XenServer5= 6Resource.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)<= br>at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.uti= l.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Sch= eduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run= (ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoo= lExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurren= t.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
2014-01-16 17:01:18,509 DEBUG [= agent.manager.DirectAgentAttache] (DirectAgent-73:null) Seq 2-1599340596: R= esponse Received:


Also, Because we were planning to upgrade the pool using Local-S= torage we start moving VM into another Primary Storage using regular proced= ure of turning off Instances, and moving them as Admin account. this keep f= ailing but also delete Instance DISK which result of having data lost.=A0

Now, we can't see our hosts list and System VM list= from the Infrastructure tab (see attachements), we only see ERROR.

here is the apilog.log when trying to show hosts:

2014-01-16 17:13:35,337 INFO=A0 [cloud.api.ApiServer= ] (catalina-exec-18:null) (userId=3D2 accountId=3D2 sessionId=3D4F907F8E77B= E76ADF46BB4FBE6B23BC0) 172.24.0.20 -- GET command=3DlistHosts&response= =3Djson&sessionkey=3DtPdf1uSuogiM1ubmRFuPuFV%2FLzM%3D&page=3D1&= pageSize=3D20&type=3Drouting&listAll=3Dtrue&_=3D1389910415201 5= 30 null


is their any other logs to look at to understands= what's broken because the upper stacktrace is clueless for me and thei= r is no errors in the management-server.log when trying to display hosts.

Regards,

Pierre-Luc Dion
Architecte de Solution Cloud | Cloud Solutions Architect
514-447-3456, 1101
- - -
CloudOps
420 rue Gu= y
Montr=E9al=A0QC =A0H3J 1S6
www.cloudops.com
@CloudOps_


--089e0112c1ba5977d404f01dc7f8-- --089e0112c1ba5977d804f01dc7fa--