Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Tue, 23 Jul 2013 17:35:12 +0200 (CEST)
From: Pierre Benard <pierre.benard@inria.fr>
To: users@cloudstack.apache.org
Message-ID: <67796534.2067987.1374593712780.JavaMail.root@inria.fr>
In-Reply-To: 
 <CALuK5bG6tp6oGJARaac8Lmuscd8GdjuntJO8ob+RG=kEfSfyFA@mail.gmail.com>
Subject: Re: Cloudstack can't deploy new vm
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

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:jo=
b-10294) Exception while executing StopVMCmd:
com.cloud.utils.exception.CloudRuntimeException: We cannot stop VM[User|i-4=
51-2756-VM] when it is in state Starting
=09at com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineMana=
gerImpl.java:1005)
=09at com.cloud.vm.UserVmManagerImpl.stopVirtualMachine(UserVmManagerImpl.j=
ava:2776)
=09at com.cloud.event.ActionEventCallback.intercept(ActionEventCallback.jav=
a:32)
=09at com.cloud.api.commands.StopVMCmd.execute(StopVMCmd.java:114)
=09at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:132)
=09at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:42=
7)
=09at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:47=
1)
=09at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
=09at java.util.concurrent.FutureTask.run(FutureTask.java:166)
=09at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.=
java:1110)
=09at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor=
.java:603)
=09at java.lang.Thread.run(Thread.java:679)


Regards,


Pierre

----- Mail original -----
> De: "Kirk Jantzer" <kirk.jantzer@gmail.com>
> =C3=80: "Cloudstack users mailing list" <users@cloudstack.apache.org>
> Envoy=C3=A9: Mardi 23 Juillet 2013 17:21:37
> Objet: Re: Cloudstack can't deploy new vm
>=20
> Sorry, saw you're on v3. the correct location is:
> /var/log/cloud/management/management-server.log
>=20
>=20
> On Tue, Jul 23, 2013 at 11:20 AM, Kirk Jantzer
> <kirk.jantzer@gmail.com>wrote:
>=20
> > 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
> > <pierre.benard@inria.fr>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" <ramindani@h2osoftwares.com>
> >> > =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
> >> > <pierre.benard@inria.fr>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
> >
>=20
>=20
>=20
> --
> Regards,
>=20
> Kirk Jantzer
> c: (678) 561-5475
> http://about.met/kirkjantzer
>=20