Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C710511C02 for ; Thu, 18 Sep 2014 21:34:26 +0000 (UTC) Received: (qmail 93111 invoked by uid 500); 18 Sep 2014 21:34:26 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 93063 invoked by uid 500); 18 Sep 2014 21:34:26 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 93043 invoked by uid 99); 18 Sep 2014 21:34:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2014 21:34:25 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mike.tutkowski@solidfire.com designates 209.85.214.176 as permitted sender) Received: from [209.85.214.176] (HELO mail-ob0-f176.google.com) (209.85.214.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Sep 2014 21:33:59 +0000 Received: by mail-ob0-f176.google.com with SMTP id uz6so1019435obc.35 for ; Thu, 18 Sep 2014 14:33:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=SntDwl67EBnKJXhiv7qBWXyB5oP9wrvniugmy+nOMYs=; b=QiJt7Zmd8BokVJEzeyrvqCKK04Rk70up7iWEr4+YaU8MlK/QOE2DaFmO3Nzxrf1Q6v HurOw9wL90pwjJkScvq41DE2Sg54k2xgg4EXLT24q/1QR3evk0N1hTlxAlk3eum41LWz noJK+5qXmgl4fl1C+jIKGhPEOz5fydx06nSTZMzKMSQBe6Msi0E0vNw9NTnMcrGoC4ae G49N5tITrDg8QwcZCuimUj5pfd5PBMdhNXb3qTyG0xIHTn4IcGW73q8bVn3uZ7EebcOr 2tZKq8OXJBsQMwr0+juHdOl2ksHrH14TM6vHrecui3+1lTa/IuxTJYepnh/4Y5BumesC VhjA== X-Gm-Message-State: ALoCoQmxgktmPGiTEPE+JljRnI89npXomXoPjNqPoVdOLIj371EDcDNhJjoowAflKl4slHjFRjRN MIME-Version: 1.0 X-Received: by 10.182.236.225 with SMTP id ux1mr1918588obc.57.1411076038267; Thu, 18 Sep 2014 14:33:58 -0700 (PDT) Received: by 10.182.24.106 with HTTP; Thu, 18 Sep 2014 14:33:58 -0700 (PDT) In-Reply-To: References: Date: Thu, 18 Sep 2014 15:33:58 -0600 Message-ID: Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System VMs with Vmware setup with CS server From: Mike Tutkowski To: "dev@cloudstack.apache.org" Cc: ilya musayev , Koushik Das , Sateesh Chodapuneedi , Adip Shetty Content-Type: multipart/alternative; boundary=001a11c2fad0036ed405035dbeef X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2fad0036ed405035dbeef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The instructions to seed secondary storage for VMware look like this: /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tm= plt \ -m /mnt/secondary \ -u http://cloudstack.apt-get.eu/systemvm/4.4/systemvm64template-4.4.0-6-vmw= are.ova \ -h vmware \ -s \ -F For -m, I have /export/secondary (not /mnt/secondary). I assume that's correct because that is, in fact, where my secondary storage system template is located for XenServer and that seems to work just fine. On Thu, Sep 18, 2014 at 3:20 PM, Mike Tutkowski < mike.tutkowski@solidfire.com> wrote: > I'm not getting far enough along in the process to repro (or not) the > problem. > > I do have a /mnt/sec folder (and I even made it 777). > > Any thoughts on this? > > WARN [c.c.s.r.VmwareStorageProcessor] (DirectAgent-46:ctx-fdd23ec9 > 192.168.129.71, job-95/job-123, cmd: CopyCommand) Exception: tar > --no-same-owner -xf /mnt/sec/template/tmpl/1/8//routing-8.ova > java.io.IOException: Cannot run program "tar" (in directory > "/mnt/sec/template/tmpl/1/8"): error=3D2, No such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041) > at com.cloud.utils.script.Script.execute(Script.java:195) > at com.cloud.utils.script.Script.execute(Script.java:163) > at com.cloud.storage.res > > On Wed, Sep 17, 2014 at 2:53 PM, Mike Tutkowski < > mike.tutkowski@solidfire.com> wrote: > >> You're right, Marcus. Now that I think about it, asserts are ignored by >> default. >> >> On Wed, Sep 17, 2014 at 1:59 PM, Marcus wrote: >> >>> Aren't asserts ignored by default? I think we had an issue with asserts >>> in >>> the past, and I believe at the time the default config had asserts >>> disabled. >>> >>> >>> On Wed, Sep 17, 2014 at 1:35 PM, Ritu Sabharwal >>> wrote: >>> >>> > Hi Mike, >>> > >>> > I updated the master just now and tried the setup. I see the same >>> error on >>> > same line number. >>> > >>> > Thanks & Regards, >>> > Ritu S. >>> > >>> > -----Original Message----- >>> > From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com] >>> > Sent: Tuesday, September 16, 2014 8:32 PM >>> > To: dev@cloudstack.apache.org >>> > Cc: ilya musayev; Koushik Das; Sateesh Chodapuneedi; Adip Shetty >>> > Subject: Re: [VMWARE SETUP ERROR] Error seeing in brining up System V= Ms >>> > with Vmware setup with CS server >>> > >>> > Can you tell us what commit SHA you are running under? >>> > >>> > I just updated master and line 2094 in VmwareResource is the followin= g: >>> > >>> > String[] diskChain =3D diskInfo.getDiskChain(); >>> > >>> > The only candidate for a NullPointerException there is diskInfo; >>> however, >>> > the previous line would have caught this as it looks like this: >>> > >>> > assert (diskInfo !=3D null); >>> > >>> > That being the case, I'm curious what commit SHA you saw this on? >>> > >>> > Thanks! >>> > >>> > On Tue, Sep 16, 2014 at 5:22 PM, Ritu Sabharwal >>> > wrote: >>> > >>> > > Hi Sateesh, Koushik, >>> > > >>> > > I am setting up Vmware Cluster with CS (master) and seeing errors. >>> > > ilya was helping me for this setup and figured out this error. >>> > > >>> > > The System VMs(Secondary Stogare VM and Console Proxy VM) are not >>> > > coming up properly. The system vms are reconfiguring and destroying >>> > > again and again in cycle. >>> > > >>> > > I have used Vmware Vsphere 5.1 SDK for building CS. >>> > > >>> > > The error logs give this error: >>> > > >>> > > 2014-09-16 16:11:01,619 WARN [c.c.h.v.r.VmwareResource] >>> > > (DirectAgent-8:ctx-8909215e 10.24.41.149, job-54/job-68, cmd: >>> > > StartCommand) StartCommand failed due to Exception: >>> > > java.lang.NullPointerException >>> > > Message: null >>> > > >>> > > java.lang.NullPointerException >>> > > at >>> > > >>> > >>> com.cloud.hypervisor.vmware.resource.VmwareResource.postDiskConfigBefor= eStart(VmwareResource.java:2094) >>> > > at >>> > > >>> > >>> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResou= rce.java:1685) >>> > > at >>> > > >>> > >>> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(Vmwa= reResource.java:448) >>> > > at >>> > > >>> > >>> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgen= tAttache.java:294) >>> > > at >>> > > >>> > >>> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(Mana= gedContextRunnable.java:49) >>> > > at >>> > > >>> > >>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call= (DefaultManagedContext.java:56) >>> > > at >>> > > >>> > >>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWi= thContext(DefaultManagedContext.java:103) >>> > > at >>> > > >>> > >>> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWit= hContext(DefaultManagedContext.java:53) >>> > > at >>> > > >>> > >>> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(Manage= dContextRunnable.java:46) >>> > > at >>> > > >>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) >>> > > at java.util.concurrent.FutureTask.run(FutureTask.java:262) >>> > > at >>> > > >>> > >>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.ac= cess$201(ScheduledThreadPoolExecutor.java:178) >>> > > at >>> > > >>> > >>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.ru= n(ScheduledThreadPoolExecutor.java:292) >>> > > at >>> > > >>> > >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.ja= va:1145) >>> > > at >>> > > >>> > >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.j= ava:615) >>> > > at java.lang.Thread.run(Thread.java:744) >>> > > >>> > > Please help to resolve this issue. >>> > > >>> > > Thanks & Regards, >>> > > Ritu S. >>> > > >>> > > >>> > >>> > >>> > -- >>> > *Mike Tutkowski* >>> > *Senior CloudStack Developer, SolidFire Inc.* >>> > e: mike.tutkowski@solidfire.com >>> > o: 303.746.7302 >>> > Advancing the way the world uses the cloud >>> > *=E2=84=A2* >>> > >>> >> >> >> >> -- >> *Mike Tutkowski* >> *Senior CloudStack Developer, SolidFire Inc.* >> e: mike.tutkowski@solidfire.com >> o: 303.746.7302 >> Advancing the way the world uses the cloud >> *=E2=84=A2* >> > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkowski@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the cloud > *=E2=84=A2* > --=20 *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkowski@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud *=E2=84=A2* --001a11c2fad0036ed405035dbeef--