NetarchiveSuite|
⇤ ← Revision 1 as of 2010-03-05 11:31:22
Size: 1121
Comment:
|
Size: 1199
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 27: | Line 27: |
| ... 0 rows selected |
|
| Line 29: | Line 33: |
| ... 0 rows selected |
|
| Line 30: | Line 38: |
... 3 rows selected |
Use ssh to go the admin machine and into your installation directory (netarkivet.dk -> kb-test-adm-001, and /home/test/TESTX)
Check that no admin.data file exists.
Check that a database directory, adminDB, exists.
Check the port number for the database by running the command:
> more conf/start_external_database.sh
It should give a line like:
java -cp $INSTALLDIR/lib/db/derby.jar:$INSTALLDIR/lib/db/derbynet.jar org.apache.derby.drda.NetworkServerControl -p 8139 start ...
The port in this case is 8139.
Log into the database and check the status (it is an external database, so the applications does not need to be shutdown before accessing the database).
> java -cp lib/db/derbyclient-10.4.2.0.jar:lib/db/derbytools-10.4.2.0.jar org.apache.derby.tools.ij
> connect 'jdbc:derby://localhost:$PORT/adminDB'
Check the content of the different tables. The file table and the replicafileinfo table should be empty, whereas the replica table should contain the replicas:
> SELECT * FROM file;
...
0 rows selected
> SELECT * FROM replicafileinfo;
...
0 rows selected
> SELECT * FROM replica;
...
3 rows selected