Hi alex,

i looked in your log, but there isn't anything special, those exceptions
"..sequoiaSABase' doesn't exist" are sounding familiar to me,
i can remember, that i had them to some time ago. But they weren't a
show stopper.

I try to find some time today looking into the codebase to see where it
hangs.

In the meantime please try to use hsqldb as recovery log, that has many
advantages in my opinion and maybe it fixes your problems. just change
the recovery log jdbc url to

 <RecoveryLog driver="org.hsqldb.jdbcDriver"
                        
url="jdbc:hsqldb:file:@DATA_DIR@/recoveryDB;shutdown=true;hsqldb.default_table_type=cached"
                         login="" password="">

stefan

Alex wrote:
> Stefan Lischke wrote:
>> Ok,
>>
>> can you send your last lines of your full cluster log
>>   
> Hi Stefan
>
> I've turned every INFO in the log4j configuration to DEBUG in order to
> get more info out.
> So when I run the controller, then execute the following at the console:
>
> Launching the Sequoia controller console
> Initializing Controller module...
> Initializing VirtualDatabase Administration module...
> Initializing SQL Console module...
> Sequoia driver (Sequoia core v2.10.9) successfully loaded.
> localhost:1090 > load virtualdatabase configuration /opt/sequoia/config/
> virtualdatabase/myDB.xml init
> XML file /opt/sequoia/config/virtualdatabase/myDB.xml successfully
> sent to Sequoia controller.
> localhost:1090 > admin myDB
> Virtual database Administrator Login > admin
> Virtual database Administrator Password >
> Ready to administrate virtual database myDB
> myDB(admin) > expert on
> Expert mode on
> myDB(admin) > initialize backend1
> Virtual Database myDB has been successfully initialized from backend
> backend1
> myDB(admin) > backup backend1 init_dump5 MySQLBackuper /tmp/backup
> Backend login for backup process > root
> Backend password for backup process >
> Backup backend backend1 in dump file init_dump5
> myDB(admin) > enable backend1
> Enabling backend backend1 from its last known checkpoint
>
>
> .. then the controller's log output can be seen here:
>
> http://ohmslaw.org.uk/controllerLog.txt
>
> Alex
>
>
>
> _______________________________________________
> Sequoia mailing list
> [email protected]
> https://forge.continuent.org/mailman/listinfo/sequoia

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to