From users-return-8442-apmail-cloudstack-users-archive=cloudstack.apache.org@cloudstack.apache.org Tue Jul 23 16:06:22 2013 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 502801083A for ; Tue, 23 Jul 2013 16:06:22 +0000 (UTC) Received: (qmail 99216 invoked by uid 500); 23 Jul 2013 16:06:21 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 99055 invoked by uid 500); 23 Jul 2013 16:06:21 -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 99045 invoked by uid 99); 23 Jul 2013 16:06:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jul 2013 16:06:20 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [192.134.164.104] (HELO mail3-relais-sop.national.inria.fr) (192.134.164.104) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Jul 2013 16:06:13 +0000 X-IronPort-AV: E=Sophos;i="4.89,728,1367964000"; d="scan'208";a="22035386" Received: from zmbs2.inria.fr ([128.93.142.15]) by mail3-relais-sop.national.inria.fr with ESMTP; 23 Jul 2013 18:05:53 +0200 Date: Tue, 23 Jul 2013 18:05:53 +0200 (CEST) From: Pierre Benard To: users@cloudstack.apache.org Message-ID: <194936096.2075232.1374595553024.JavaMail.root@inria.fr> In-Reply-To: Subject: Re: Cloudstack can't deploy new vm MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [131.254.12.237] X-Mailer: Zimbra 7.2.4_GA_2900 (ZimbraWebClient - GC28 (Linux)/7.2.4_GA_2900) X-Virus-Checked: Checked by ClamAV on apache.org Yes it's all. We have no log for 22th. I've activated the debug level log the last week and i've restarted the ser= vice after, cf : #sed -i 's/INFO/DEBUG/g' /etc/cloud/management/log4j-cloud.xml #service cloud-management restart Tomorrow, I could probably reboot my cloudstackserver between 9am and 12am = (GMT+1 Paris). I'll send you the log after that. Regards, Pierre ----- Mail original ----- > De: "Kirk Jantzer" > =C3=80: "Cloudstack users mailing list" > Envoy=C3=A9: Mardi 23 Juillet 2013 17:53:16 > Objet: Re: Cloudstack can't deploy new vm >=20 > That's all that's in your log? >=20 >=20 > On Tue, Jul 23, 2013 at 11:35 AM, Pierre Benard > wrote: >=20 > > Hi, > > > > The log is really short for today (we've made some creating tests > > today): > > > > 2013-07-23 14:55:58,608 ERROR [cloud.server.ManagementServerImpl] > > (catalina-exec-10:null) Incorrect format of the template id 460 > > 2013-07-23 14:55:59,858 ERROR [cloud.server.ManagementServerImpl] > > (catalina-exec-6:null) Incorrect format of the template id 439 > > > > The precedent log is dated on 21th, and it is short too : > > > > 2013-07-21 15:17:08,664 ERROR [cloud.api.ApiDispatcher] > > (Job-Executor-32:job-10294) Exception while executing StopVMCmd: > > com.cloud.utils.exception.CloudRuntimeException: We cannot stop > > VM[User|i-451-2756-VM] when it is in state Starting > > at > > com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManage= rImpl.java:1005) > > at > > com.cloud.vm.UserVmManagerImpl.stopVirtualMachine(UserVmManagerImpl.jav= a:2776) > > at > > com.cloud.event.ActionEventCallback.intercept(ActionEventCallback.java:= 32) > > at > > com.cloud.api.commands.StopVMCmd.execute(StopVMCmd.java:114) > > at > > com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:132) > > at > > com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:427) > > 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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.ja= va:1110) > > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.j= ava:603) > > at java.lang.Thread.run(Thread.java:679) > > > > > > Regards, > > > > > > Pierre > > > > ----- Mail original ----- > > > De: "Kirk Jantzer" > > > =C3=80: "Cloudstack users mailing list" > > > Envoy=C3=A9: Mardi 23 Juillet 2013 17:21:37 > > > Objet: Re: Cloudstack can't deploy new vm > > > > > > Sorry, saw you're on v3. the correct location is: > > > /var/log/cloud/management/management-server.log > > > > > > > > > On Tue, Jul 23, 2013 at 11:20 AM, Kirk Jantzer > > > wrote: > > > > > > > Please paste the contents > > > > of /var/log/cloudstack/management/management-server.log to > > > > PasteBin > > > > so that > > > > we can analyze that. > > > > > > > > > > > > On Tue, Jul 23, 2013 at 11:10 AM, Pierre Benard > > > > wrote: > > > > > > > >> Hi, > > > >> > > > >> Thank you for your answer. > > > >> > > > >> Our virtual router vm was used @50% of CPU and the network > > > >> traffic > > > >> it was > > > >> amazing. > > > >> We had some system scripts who send DNS request storm on > > > >> virtual > > > >> router. > > > >> Now, we have corrected this and now the usage of cpu is under > > > >> 1% > > > >> and > > > >> network traffic is "normal". > > > >> > > > >> But, this operation don't be resolving our problems of new > > > >> instance > > > >> deployment :-( > > > >> > > > >> Somebody has an other idea ? > > > >> > > > >> Thanks in advance. > > > >> > > > >> Pierre > > > >> > > > >> ----- Mail original ----- > > > >> > De: "ramnivas indani" > > > >> > =C3=80: users@cloudstack.apache.org > > > >> > Envoy=C3=A9: Mardi 23 Juillet 2013 10:27:11 > > > >> > Objet: Re: Cloudstack can't deploy new vm > > > >> > > > > >> > We also face this kind of problem many times but in our case > > > >> > its > > > >> > because of > > > >> > router or storage instance are disconnected or down under > > > >> > vmware, i > > > >> > will > > > >> > suggest you to check their connectivity once not only from > > > >> > cloudstack > > > >> > but > > > >> > also from backend. > > > >> > > > > >> > > > > >> > On Tue, Jul 23, 2013 at 1:50 PM, Pierre Benard > > > >> > wrote: > > > >> > > > > >> > > Hi, > > > >> > > > > > >> > > > > > >> > > > > > >> > > We have a problem with our CloudStack. > > > >> > > We can't deploying new instance. When we try to deploy new > > > >> > > vm > > > >> > > we > > > >> > > have a > > > >> > > short error message on the CloudStack interface : "Unable > > > >> > > to > > > >> > > create > > > >> > > a > > > >> > > deployment for VM[User|i-3-2764-VM]" . We have the same > > > >> > > error > > > >> > > when > > > >> > > we > > > >> > > deploy new instance from iso or template. > > > >> > > In the event page on CS, we have : > > > >> > > > > > >> > > VM.CREATE Error while starting Vm. Vm Id: 2764 > > > >> > > pierre.benard@inria.fr 22 Jul 2013 13:15:47 > > > >> > > VM.CREATE Starting job for starting Vm. Vm Id: 2764 > > > >> > > pierre.benard@inria.fr 22 Jul 2013 13:15:47 > > > >> > > VM.CREATE Scheduled async job for starting Vm. Vm > > > >> > > Id: > > > >> > > 2764 > > > >> > > pierre.benard@inria.fr 22 Jul 2013 13:15:46 > > > >> > > VM.CREATE Successfully created entity for deploying > > > >> > > Vm. > > > >> > > Vm > > > >> > > Id: 2764 > > > >> > > pierre.benard@inria.fr 22 Jul 2013 13:15:46 > > > >> > > > > > >> > > Isn't really verbose ... > > > >> > > > > > >> > > > > > >> > > All the other instance are continuous to running > > > >> > > correctly, we > > > >> > > can > > > >> > > stop/start it. > > > >> > > There is no significant error in the log files of > > > >> > > CloudStack > > > >> > > server > > > >> > > and on > > > >> > > each we sufficient resources to deploy many instances. > > > >> > > The SSVM and primary storage are available. > > > >> > > > > > >> > > > > > >> > > Our CloudStack environment : > > > >> > > * CloudStack v3 > > > >> > > * 1 pod of 4 clusters KVM, each cluster has 4 KVM > > > >> > > hypervisor > > > >> > > > > > >> > > > > > >> > > Please Suggest. > > > >> > > > > > >> > > > > > >> > > Thank you. > > > >> > > > > > >> > > > > > >> > > Pierre B=C3=A9nard > > > >> > > System engineer > > > >> > > > > > >> > > > > > >> > > Inria Rennes - Bretagne Atlantique > > > >> > > > > > >> > > Campus universitaire de Beaulieu > > > >> > > 35042 Rennes Cedex > > > >> > > T=C3=A9l. +33 2 99 84 71 00 > > > >> > > Fax +33 2 99 84 71 71 > > > >> > > www.inria.fr > > > >> > > > > > >> > > Suivez=E2=80=90nous sur : > > > >> > > Twitter twitter.com/inria > > > >> > > YouTube youtube.com/inriachannel > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > >> > > > > > > > > > > > > > > > > -- > > > > Regards, > > > > > > > > Kirk Jantzer > > > > c: (678) 561-5475 > > > > http://about.met/kirkjantzer > > > > > > > > > > > > > > > > -- > > > Regards, > > > > > > Kirk Jantzer > > > c: (678) 561-5475 > > > http://about.met/kirkjantzer > > > > > >=20 >=20 >=20 > -- > Regards, >=20 > Kirk Jantzer > c: (678) 561-5475 > http://about.met/kirkjantzer >