Caleb, Take the database ID of the CPVM v-XX-VM and run the following:
Update vm_instance set status = stopped where id = XX; That will change it to stopped in the UI under the infrastructure tab. Do a restart and it should recreate the VM. Thanks, Matt -----Original Message----- From: Caleb Call [mailto:calebc...@me.com] Sent: Tuesday, February 12, 2013 3:53 PM To: cloudstack-users@incubator.apache.org; aemne...@gmail.com Subject: Re: launch console proxy Vm 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 <aemne...@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.child...@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.child...@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 >>> >>> >>
