Return-Path: X-Original-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C094EEAF2 for ; Tue, 12 Feb 2013 19:55:11 +0000 (UTC) Received: (qmail 45465 invoked by uid 500); 12 Feb 2013 19:55:10 -0000 Delivered-To: apmail-incubator-cloudstack-users-archive@incubator.apache.org Received: (qmail 45427 invoked by uid 500); 12 Feb 2013 19:55:10 -0000 Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-users@incubator.apache.org Delivered-To: mailing list cloudstack-users@incubator.apache.org Received: (qmail 45419 invoked by uid 99); 12 Feb 2013 19:55:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2013 19:55:10 +0000 X-ASF-Spam-Status: No, hits=-1.6 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.149.18] (HELO na3sys009aog137.obsmtp.com) (74.125.149.18) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Feb 2013 19:55:02 +0000 Received: from mail-yh0-f69.google.com ([209.85.213.69]) (using TLSv1) by na3sys009aob137.postini.com ([74.125.148.12]) with SMTP ID DSNKURqeAT4mg3O6U6w1NAFAaoRTDZ4KM91E@postini.com; Tue, 12 Feb 2013 11:54:42 PST Received: by mail-yh0-f69.google.com with SMTP id w68so497236yhw.0 for ; Tue, 12 Feb 2013 11:54:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:x-gm-message-state; bh=mHHnoRXGD1ON32xefYjgT4SBBVKNYxaQrFZK5NcNPc0=; b=FYAnouHqAOTiYn2w4szVFWGk4ZL2zNKfW36cRFFjLRoHaxenasl244F8c2vxVV3Zvn klj/+9jCi2dWgosy+LEwYFf0yZEPYLlSiEGM63BFSYLOEy2zxzFkc3LWcQtHiNCcavRP X8mkqvMturHe02nAi3biu+ZIFwoHAeNEcu6VgTqTxqsW2XWV+aG8zsl2tx6jeWK1t3gJ cBvE1v3KOqTmqM2FW+LiLyaNZyV3IhESfI4ld+5BVgqO7Z7DBqpm2M5hrBMPaRcH2tbO 5heDFJlnH1iqVk0VBIiLYdgUDNqtfLcdI6N9bwVki4Hy2db0hbmX1MCSe7u0PpNyTA/y zTVw== X-Received: by 10.220.231.196 with SMTP id jr4mr25993244vcb.16.1360698881204; Tue, 12 Feb 2013 11:54:41 -0800 (PST) X-Received: by 10.220.231.196 with SMTP id jr4mr25993237vcb.16.1360698881126; Tue, 12 Feb 2013 11:54:41 -0800 (PST) Received: from USLT-205755.sungardas.corp ([216.203.6.11]) by mx.google.com with ESMTPS id x9sm65866364vel.4.2013.02.12.11.54.39 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 12 Feb 2013 11:54:40 -0800 (PST) Received: by USLT-205755.sungardas.corp (Postfix, from userid 76098887) id 16E4AF538C4F; Tue, 12 Feb 2013 14:54:20 -0500 (EST) Date: Tue, 12 Feb 2013 14:54:18 -0500 From: Chip Childers To: cloudstack-users@incubator.apache.org Subject: Re: launch console proxy Vm Message-ID: <20130212195414.GB92132@USLT-205755.sungardas.corp> References: <060673D9-3D15-4DF6-8780-455B9DA2286F@me.com> <20130212194722.GA92132@USLT-205755.sungardas.corp> <8D57867B-65B6-47FE-9DF4-106EC14DF124@me.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8D57867B-65B6-47FE-9DF4-106EC14DF124@me.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Gm-Message-State: ALoCoQmVhxYGobC4fnLZErPAP6f63m3ampkBqSemLBm7TJcy0p/BU9dfO8Bdzi5UrVv0i4PcRXS9GqK7j0FjEizOZZy1gIvxIXQr9n1d3Uz7b0hvDBzBW1/E06IVZatotinythN4uj6X1mOXbEW0pz3xj9qmMkwp7cDU0DiKo262vgyY9XWTyd3URZFL+fm6zB7ZwhL0gqgl X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Feb 12, 2013 at 12:51:46PM -0700, Caleb Call wrote: > It is, but it was actually already destroyed from within the cloudstack ui so it's not listed there and hasn't been re-spawned. > Hmm... interesting. I haven't run into that. Are you able to restart the mgmt server(s) and see if that causes it to be re-spawned? Anyone else have ideas? > > On Feb 12, 2013, at 12:47 PM, Chip Childers wrote: > > > On Tue, Feb 12, 2013 at 12:43:59PM -0700, Caleb Call wrote: > >> The console proxy VM is one of our Zones was accidentally destroyed. Is there a way to force the zone to relaunch or recreate a new console proxy? It's been this way for several days, so I'm quite certain it's not going to do it on it's own. > >> > >> Thanks > >> > > > > Is the console proxy listed in the infrastructure page's system VMs > > section? If so, destroy it from there and CS should create a new one > > for you. > > > > -chip > >