Hi Nic,
Firstly, I have had to alter the controller.bat file since the path to
java needs to be in quotes otherwise it will not find the java
executable, as in:
SET JAVA="%JAVA_HOME%\bin\java”
Did you use the installer or the .zip/.tgz version?
It's always tricky to handle the path in Windows since long names and
spaces are handled differently between versions.
Secondly, I am encountering the following:
org.continuent.sequoia.common.exceptions.VirtualDatabaseException:
Error while initalizing database backend 192.168.1.103
(java.sql.SQLException: Unable to connect to backend.)
You should get a more detailed error in the log giving you the reason
while the connection to the backend failed. If not, set the
DatabaseBackend logger in log4j.properties to DEBUG and retry.
This would imply that my postgres driver is not in
%SEQUOIA_HOME%/drivers, however it is in fact, and if I do a javap:
Not necessarily, if the driver could not be loaded you would have an
explicit error that the driver class cannot be loaded. It might be a
url/login/password configuration problem or an authentication problem.
I can connect ok to the database using a TestConnection class that I
wrote for a JDBC connection.
Do you connect with the same login/password/url from the same machine as
the controller?
It might also be that the connection test statement or some other test
fails but you should get more info from the log.
Why so many -Djava.net.preferIPv4Stack=true?
You might have run multiple time the scripts that systematically adds
things to JAVA_OPTIONS or a similar environment variable. I have not run
the scripts on Windows for quite some time so I don't know that the
status is right now.
<Backuper backuperName="Octopus"
className="org.continuent.sequoia.controller.backup.backupers.OctopusBackuper"
options="zip=true"/>
I would strongly discourage the use of Octopus, you should use the
Postgresql backuper instead.
<DatabaseBackend name="192.168.x.x" driver="org.postgresql.Driver"
url="jdbc:postgresql://192.168.x.x/vdb"
connectionTestStatement="select now()">
<ConnectionManager vLogin="user" rLogin="vdb" rPassword="vdb">
You understand that with this configuration, the application will use
login 'user' but Sequoia will connect to Postgres using vdb/vdb as
login/password, right?
Keep us posted with the details of the failure.
Thanks for your feedback,
Emmanuel
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
