Hi dustan, Just empty your recovery logs on every controller and your cluster will start again. Choose the node with the most writes, start it, make a dump and put the dump to all other nodes.
Remember if you stop a cluster, you have to start the cluster in the opposite way. e.g. your nodes are 1,2,3,4 you stop with sequence 2,3,1,4 you have to start node 4 first, cause he was the "last man down" hth stefan Dustan Ashley wrote: > All- > > > > I have been building out a two controller and 4 postgres backend > cluster with sequoia. I have been running through some exercises to get > a handle on how to administer the cluster properly and have run into > some issues. I tried a clean shutdown of the whole cluster, starting > with the second controller. I issued the shutdown virtualdatabase > command and the console hung, I checked the logs which seemed to > indicate that everything was good and that there were no waiting > transactions, but after a few hours, the console was still hung so I > terminated the console session. I went back into the console and checked > the status of the backends and they were both down and looking good. I > issued shutdown to bring the controller down and got an error that said > it was unable to shutdown the controller, but did not say the reason, > there was also no info in the logs that indicated an issue. > > The exact same thing happened when I tried to shutdown the first > controller as well. Apart from the headache this isn't a big deal as > this is not in production yet and I have good backups that I can restore > from, the problem I have now is that when I go to start controller2 I > get an error about "Not Starting VDB (Not the last man down)" this error > also appears when starting controller1. I can't begin to restore from my > backups, because neither controller will load the VDB config file. So I > was wondering if there was any way to force the controller to load the > VDB config file so that I can reinitialize my databases. > > > > Thank you- > > Dustan > > > > > +----------------------------------------------------------------------+ > | Z1 SecureMail Gateway Info - http://www.zertificon.com | > +----------------------------------------------------------------------+ > | - Die Nachricht war weder verschluesselt noch digital unterschrieben | > +----------------------------------------------------------------------+ > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Sequoia mailing list > [email protected] > https://forge.continuent.org/mailman/listinfo/sequoia
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
