Hi again
Earlier I had backends being enabled without any problem - and the
command returns almost instantly - but now the console hangs if I try to
enable a backend.
Firstly, I'm deleting the tables from the recovery database to avoid
confusion.
Then I run a controller.
Then I run console commands as follows, on same machine:
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 > show virtualdatabases
localhost:1090 > load virtualdatabase configuration /opt/sequoia/con
config/virtualdatabase/myDB.xml init
XML file /opt/sequoia/config/virtualdatabase/myDB.xml successfully sent
to Sequoia controller.
localhost:1090 > show virtualdatabases
myDB
localhost:1090 > admin myDB
Virtual database Administrator Login > admin
Virtual database Administrator Password >
Ready to administrate virtual database myDB
myDB(admin) > initialize backend1
Virtual Database myDB has been successfully initialized from backend
backend1
myDB(admin) > enable backend1
Enabling backend backend1 from its last known checkpoint
And then I'm stuck at this point - console is waiting on something to
happen forever..
The controller's output is as follows:
18:01:13,390 INFO controller.core.Controller Loading configuration
file: /opt/sequoia-2.10.9-bin/config/controller/controller.xml
18:01:13,491 INFO controller.core.Controller JMX is enabled
18:01:13,519 INFO controller.core.Controller Starting JMX server on
host: 192.168.0.128
18:01:13,670 INFO controller.core.Controller Waiting for connections on
0.0.0.0:25322
18:01:13,680 INFO controller.core.Controller Controller started on
2007.10.19 42 at 06:01:13 PM BST
18:01:13,680 INFO controller.core.Controller Controller
192.168.0.128:25322 ready, listening to requests ...
18:01:34,458 INFO controller.backup.BackupManager Registering backuper
MySQLBackuper to handle format MySQL raw dump
18:01:34,485 INFO DatabaseBackend.myDB.backend1 Adding connection
manager for virtual user "user"
18:01:35,031 INFO controller.RequestManager.myDB Request manager will
parse requests with the following granularity: TABLE
18:01:35,043 INFO controller.virtualdatabase.myDB Recovery log size: 0
18:01:35,044 INFO controller.virtualdatabase.myDB Using Hedera
properties file: /hedera_jgroups.properties
-------------------------------------------------------
GMS: address is 192.168.0.128:32851
-------------------------------------------------------
18:01:39,711 INFO controller.virtualdatabase.myDB Group myDB connected
to Member(address=/192.168.0.128:32851, uid=myDB)
18:01:39,711 INFO controller.virtualdatabase.myDB First controller in
group myDB
18:01:39,715 WARN controller.RequestManager.myDB Backend backend1 was
not properly stopped, manual recovery will be needed (Backend:backend1,
VirtualDatabase:myDB, State:disabled, Checkpoint:)
18:01:39,717 INFO sequoia.controller.recoverylog Checking recovery log
consistency
18:01:39,724 INFO controller.core.Controller Adding VirtualDatabase myDB
18:02:20,004 INFO DatabaseBackend.myDB.backend1 Detected backend as: MySQL
18:02:20,097 INFO controller.RequestManager.myDB Setting new virtual
database schema.
18:02:20,115 INFO controller.recoverylog.RecoverThread Starting recovery
When I finally do CTRL-C to escape from the hung console, I see the error:
Error unmarshaling return header; nested exception is:
java.io.EOFException
myDB(admin) >
cheers,
Alex
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
