Hi Warren, Go into your new database and run:
Update vm_instances set state = "stopped" where id = #; # is the is id # in s-#-VM. Then you have two choices. 1 you can just start it from there and let it recreate. Or 2. Destroy it and let the cloud rebuild it. Hope that helps, Matt On Apr 22, 2013, at 7:50 AM, "Warren Nicholson" <warren.nichol...@nfinausa.com> wrote: > I'm trying to write a procedure to replace the management controller > > in case of a failure. > > > > I have set up the replacement server identically (Centos, NICs, Cloudstack). > > > > I then exported the database files (Cloud, Cloud_Usage, MySQL) from the > original > > and imported them into the replacement. > > > > Everything seemed to work (templates, Primary, Secondary), except the SSVM > and > > the Console Proxy are stuck in "stopping" state. According to the > management-server.log > > file, it is detecting the old SSVM is in stopping state and prefers to just > wait and let it resolve > > itself, which it never does. > > > > Suggestions? > > > > Warren >
