Thanks so much Oliver. I was able to figure it out last night and get the VDB up and running with a 1 controller and 1 PostgreSQL DB backend running. I was pretty happy about that. =) Thank you for pointing me in the right direction there!
I'm actually pretty grateful to have the "console" feature. That allows finer grained control and I like that. Thank you again! Warm regards, Jordan Michaels Vivio Technologies http://www.viviotech.net/ BlueDragon Alliance Member [EMAIL PROTECTED] Olivier Fambon wrote: > Jordan Michaels [03/10/07 02:53]: > ... >> However, I'm getting this error when I try to run the controller.sh >> script to just start up the controller. I'll play with it a bit and see >> if I can set it up so that the VDB isn't attempting to auto-load on the >> controller startup. > > Aha, then you probably have a VirtualDatabase element defined in > controller.xml in <install dir>/config/controller/ with your demo vdb > declared in it. > > Now for the politics: the "default recommended usage" is to not > auto-load vdbs at controller startup... Actually this auto-load thing > is a very handy feature, but in the general case controllers are > expected to host several vdbs and remain up "forever" and you never > really know which vdb was stopped in which order. > > Should you wish to use the auto-load feature, you then want to ensure > proper restart-ordering - of all vdbs - by starting the controllers in > the right order. > > HTH, > > Olivier. > _______________________________________________ > Sequoia mailing list > [email protected] > https://forge.continuent.org/mailman/listinfo/sequoia > > _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
