Stefan Lischke wrote:
Ok,
can you send your last lines of your full cluster log
Hi Stefan
Ok, here's what the cluster log shows for the entire "start controller
and run those given console commands" session:
2007-10-22 12:00:48,394 INFO Controller 192.168.0.128:25322 ready,
listening to requests ...
2007-10-22 12:01:22,208 INFO Loading virtual databases configuration
file (init)
2007-10-22 12:01:27,709 INFO The virtual database myDB has been
successfully added to the controller.
2007-10-22 12:01:27,709 INFO Loading of virtual databases configuration
file has been successful (init)
2007-10-22 12:01:27,851 INFO Virtual database myDB is initializing from
database backend backend1
2007-10-22 12:01:27,859 INFO Database backend myDB.backend1 is now in
state disabled
2007-10-22 12:01:27,872 INFO Virtual database myDB initialization from
database backend backend1 completed
2007-10-22 12:01:27,989 INFO Virtual database myDB is backuping
database backend backend1 with dump name init_dump
2007-10-22 12:01:27,998 INFO Database backend myDB.backend1 is now in
state backing up
2007-10-22 12:01:28,077 INFO Database backend myDB.backend1 is now in
state disabled
2007-10-22 12:01:28,080 INFO Virtual database myDB successfully
backuped database backend backend1 with dump name init_dump
2007-10-22 12:01:28,112 INFO Virtual database myDB is enabling database
backend backend1 from checkpoint
2007-10-22 12:01:28,348 INFO Database backend myDB.backend1 is now in
state replaying
So presumably it's hung at this replaying stage when I enable it.
Replaying is how a backend catches up with changes that happened in a
cluster while it was down, right?
thanks,
Alex
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
