This documentation explains the common operations that an administrator might need to perform on KB. It also lists common issues and their solutions.

Operations

Start KB

cd <KB_TOMCAT>/bin/
./startup.sh

Stop KB

cd <KB_TOMCAT>/bin/
./shutdown.sh

Upgrade KB

cd <KB_TOMCAT>/webapps
rm -rf  KB/
cp new-KB.war KB.war

Check KB's logs

There are 2 log files that contain useful information :

• <KB_TOMCAT>/logs/catalina.out: default log file for Tomcat. This file will contain the errors when KB fails to start
• <KB_TOMCAT>/logs/KB-API.log : log file that contains the application logs.

Adjust KB application log level

vi <KB_TOMCAT>/bin/setenv.sh 

Add the logging.level.com.mondeca  system property to the CATALINA_OPTS variable, and adjust the log level value to ERROR, WARN, INFO, DEBUG or TRACE like in the following line :
export CATALINA_OPTS="$CATALINA_OPTS -Dlogging.level.com.mondeca=TRACE"

Then restart KB.

Start Elasticsearch

Use an option from Elasticsearch startup script that writes the process id into a file, here called pid :

cd <KB_Elasticsearch>/bin
./elasticsearch -d -p pid

Stop Elasticsearch

 When the command to start Elasticsearch wrote the process into the pid file, then use the following command to stop Elasticsearch :

cd <KB_Elasticsearch>/bin
pkill -F pid

Check Elasticsearch logs

vi <KB_Elasticsearch>/logs/elasticsearch.log

Start/stop/restart Neo4j

cd <KB_Neo4j>/bin
./neo4j start|stop|restart

Check Neo4j logs

vi <KB_Neo4j>/logs/neo4j.log

Troubleshooting

Coming soon