NetarchiveSuiteUse 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.5.3.0.jar:lib/db/derbytools-10.5.3.0.jar org.apache.derby.tools.ij
ij> connect 'jdbc:derby://localhost:$PORT/adminDB' where $PORT=8139
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
> exit;
Check that the logmessages does not contain any warnings or errors.
Do following in a browser
Start Program
. Go to http://$GUIadminserver:$http-port/HarvestDefinition/
- o o where GUIadminserver and http-port are specified in the deploy configuration file under the application named dk.netarkivet.common.webinterface.GUIApplication
o In the one-machine setup (deploy_example_one_machine.xml ) the link will be : http://localhost:8074
- o o where GUIadminserver and http-port are specified in the deploy configuration file under the application named dk.netarkivet.common.webinterface.GUIApplication
- Go to the status site:
- o
- o Click on System State in the side bar.
- o
You should see no warning or errors in the logmessages.