Cheers, Robert
On 4/12/08 12:31 PM, "Todd Robinson" <[EMAIL PROTECTED]> wrote:
Question from a newbie; I've gotten the basic configuration
done and
have started the controller with out any errors. Sequoia is
running on
the same box a the database server. I can see the connection
to the
back end database and it has created the Recovery tables. But
when I
try to connect to the console port I get the following error
(other
configuration info follows):
[EMAIL PROTECTED] sequoia]# bin/console.sh
Launching the Sequoia controller console
Cannot connect to the administration port of the controller.
Is a
controller running at localhost:1090 ?
Initializing Controller module...
Initializing VirtualDatabase Administration module...
Initializing SQL Console module...
Sequoia driver (Sequoia core v2.10.9) successfully loaded.
Thanks for any help in advance,
Todd
System Configuration:
CentOS 5.1
Sun JDK 6u5
Sequoia 2.10.9
MySQL 5.0.22
[EMAIL PROTECTED] sequoia]# netstat -tpan | grep 1090
tcp 0 0 0.0.0.0:1090 0.0.0.0:*
LISTEN 14520/java
[EMAIL PROTECTED] controller]# cat controller.xml
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE SEQUOIA-CONTROLLER PUBLIC "-//Continuent//DTD
SEQUOIA-CONTROLLER 2.10.9//EN"
"http://sequoia.continuent.org/dtds/sequoia-controller-2.10.9.dtd">
<SEQUOIA-CONTROLLER>
<Controller ipAddress="127.0.0.1" port="25322">
<JmxSettings>
<RmiJmxAdaptor port="1090"/>
</JmxSettings>
<VirtualDatabase configFile="mysqldb-raidb1.xml"
virtualDatabaseName="zag1DB" autoEnableBackends="force"
checkpointName="Initial_empty_recovery_log"/>
</Controller>
</SEQUOIA-CONTROLLER>
[EMAIL PROTECTED] sequoia]# bin/controller.sh
java version "1.6.0_05"
Java(TM) SE Runtime Environment (build 1.6.0_05-b13)
Java HotSpot(TM) Client VM (build 10.0-b19, mixed mode,
sharing)
09:40:02,687 INFO controller.core.Controller Sequoia
controller
(2.10.9)
09:40:02,785 INFO controller.core.Controller Loading
configuration
file: /usr/local/sequoia/config/controller/controller.xml
09:40:02,865 INFO controller.core.Controller JMX is enabled
09:40:02,900 INFO controller.core.Controller Starting JMX
server on
host: 127.0.0.1
09:40:03,224 INFO backup.backupers.OctopusBackuper
OctopusBackuper
backup compression is set to true
09:40:03,224 INFO controller.backup.BackupManager Registering
backuper
Octopus to handle format Octopus v3.4.1 database neutral dump
compressed
09:40:03,254 INFO DatabaseBackend.zag1DB.zagamodb Adding
connection
manager for virtual user "webuser"
09:40:03,322 DEBUG sequoia.controller.recoverylog Connection
to
jdbc:mysql://localhost:3306/sequoia as user sequser
09:40:03,658 DEBUG sequoia.controller.recoverylog Log table
create
statement: CREATE TABLE RECOVERY (log_id BIGINT NOT
NULL,vlogin TEXTNOT
NULL,sqldata TEXT NOT NULL,sqldata_param TEXT,auto_conn_tran
CHAR(1) NOT
NULL,transaction_id BIGINT NOT NULL,request_id
BIGINT,exec_status
CHAR(1) NOT NULL,exec_time BIGINT,update_count INT,PRIMARY KEY
(log_id))
09:40:03,659 DEBUG sequoia.controller.recoverylog Checkpoint
table
create statement: CREATE TABLE CHECKPOINT (name CHAR(40) NOT
NULL,log_id
BIGINT,PRIMARY KEY (name))
09:40:03,659 DEBUG sequoia.controller.recoverylog Backend
table create
statement: CREATE TABLE BACKEND (database_name TEXT NOT NULL,
backend_name TEXT NOT NULL,backend_state INTEGER,
checkpoint_name
TEXTNOT NULL )
09:40:03,660 DEBUG sequoia.controller.recoverylog Dump table
create
statement: CREATE TABLE DUMP (dump_name TEXT NOT
NULL,dump_date
TIMESTAMP,dump_path TEXT NOT NULL,dump_format TEXT NOT
NULL,checkpoint_name TEXT NOT NULL,backend_name TEXT NOT
NULL,tables
TEXT NOT NULL)
09:40:03,664 DEBUG sequoia.controller.recoverylog Table found:
BACKEND
09:40:03,665 DEBUG sequoia.controller.recoverylog Table found:
CHECKPOINT
09:40:03,665 DEBUG sequoia.controller.recoverylog Retrieving
checkpoint
names list
09:40:03,684 DEBUG sequoia.controller.recoverylog Checkpoint
list...
name=[Initial_empty_recovery_log] log_id=[0]
name=[last-man-down] log_id=[0]
09:40:03,684 DEBUG sequoia.controller.recoverylog Table found:
DUMP
09:40:03,684 DEBUG sequoia.controller.recoverylog Table found:
RECOVERY
09:40:03,723 INFO controller.RequestManager.zag1DB Request
manager will
parse requests with the following granularity: TABLE
09:40:03,737 WARN controller.core.Controller Backends enabled
in force
mode from checkpoint Initial_empty_recovery_log
09:40:03,975 INFO DatabaseBackend.zag1DB.zagamodb Detected
backend as:
MySQL
09:40:03,977 WARN DatabaseBackend.zag1DB.zagamodb Unable to
test
ResultSet.getObject
09:40:04,016 INFO controller.RequestManager.zag1DB Setting
new virtual
database schema.
09:40:04,035 INFO controller.recoverylog.RecoverThread
Starting
recovery
09:40:04,042 INFO controller.recoverylog.RecoverThread
Recovery
completed
09:40:04,060 INFO controller.recoverylog.RecoverThread
Database backend
zagamodb is now enabled
09:40:04,069 INFO controller.core.Controller Adding
VirtualDatabase
zag1DB
09:40:04,080 INFO controller.core.Controller Waiting for
connections on
0.0.0.0:25322
09:40:04,088 INFO controller.core.Controller Controller
started on
2008.04.12 15 at 09:40:04 AM EDT
09:40:04,088 INFO controller.core.Controller Controller
127.0.0.1:25322
ready, listening to requests ...