Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of calebcall@me.com designates
 17.158.236.237 as permitted sender)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Subject: Re: launch console proxy Vm
From: Caleb Call <calebcall@me.com>
In-reply-to: 
 <CAK_WW3ygDHBL+oR2bfQfdg5MaF0KNcJebVkssi8HnweZtd5r_w@mail.gmail.com>
Date: Tue, 12 Feb 2013 15:20:41 -0700
Message-id: <A1CEBB36-52A5-4D06-A37A-672326BB217A@me.com>
References: <060673D9-3D15-4DF6-8780-455B9DA2286F@me.com>
 <20130212194722.GA92132@USLT-205755.sungardas.corp>
 <8D57867B-65B6-47FE-9DF4-106EC14DF124@me.com>
 <20130212195414.GB92132@USLT-205755.sungardas.corp>
 <CAO+D_1ycR+k5iCu7B8STVgDuw-TpSORvzMdEQ61ez6wh=rkHXw@mail.gmail.com>
 <5AF4FFE5-D708-473C-AF4B-4B80E1A085B5@me.com>
 <CAK_WW3ygDHBL+oR2bfQfdg5MaF0KNcJebVkssi8HnweZtd5r_w@mail.gmail.com>
To: cloudstack-users@incubator.apache.org

I tried that, there was a little more to it than that.  I had to up that the vm_instance table as well as update the host table.  It still doesn't show up in the GUI, so I tried to start using the API but it fails.

On Feb 12, 2013, at 2:13 PM, Jaro 2079 <jaro2079@gmail.com> wrote:

> maybe try undelete in database....
> set on vm_instance table state to "Stopped" and removed to NULL then start
> vm from GUI
> if volumen exist vm could start
> 
> 2013/2/12 Caleb Call <calebcall@me.com>
> 
>> We've restarted the management service many times, let me dig though the
>> logs and see what info I can pull out and see if it's even trying to start
>> it back up (I haven't seen anything to suggest it trying, but the logs are
>> large).
>> 
>> Here's a feature request, breaking logging out to individual zone files.
>> Having several zones logging to a single management log file makes for a
>> messy log file! :)
>> 
>> One thought we had was to run the cloud-sysvmadm command to see if that
>> would force it to restart, but it didn't, it just restarted all the other
>> system vms.
>> 
>> On Feb 12, 2013, at 1:09 PM, Ahmad Emneina <aemneina@gmail.com> wrote:
>> 
>>> do the logs show the management server trying to start the console proxy?
>>> if not I'd also restart the management service, see if you get any
>> further
>>> with that. If there are logs, it might help to post as much of the
>>> management server log as possible.
>>> 
>>> 
>>> On Tue, Feb 12, 2013 at 11:54 AM, Chip Childers
>>> <chip.childers@sungard.com>wrote:
>>> 
>>>> 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 <chip.childers@sungard.com
>>> 
>>>> 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
>>>>> 
>>>>> 
>>>> 
>> 
>>