Basic Administration and Install Validation

This section describes the process of Administering Owl setup and running your first Owlchecks. In order to administer Owl it is important the administrator has a basic understanding of the Linux operating system, commands, and troubleshooting tactics.

Administration of Owl services

Administration of owl begins with making sure all components are running appropriately. As mentioned in this installation section of this document an administrator can start all owl services by using the script <INSTALL_PATH>/bin/owlmanage.sh start. Validation of services can be achieved by checking <INSTALL_PATH>/pids/ which lists thel pid files generated when the administrator starts up owl. Here is a sample list of pids:

• postgres.pid

• orient.pid

• owl-web.pid

• owl-agent.pid

Likewise an administrator can execute a command when changed directory into “pids” as follows:

for pidfile in `ls *.pid`; do FILEPID=$(echo `cat $pidfile` | cut -d . -f1); echo `ps -aef | grep -i $FILEPID`; done;

The output of this command will look something like the below

ec2-user 19169 1 17 17:44 pts/0 00:07:12 /home/ec2-user/jdk1.8.0_131/bin/java -server -Xms2G -Xmx2G -Djna.nosys=true -XX:+HeapDumpOnOutOfMemoryError -Djava.awt.headless=true -Dfile.encoding=UTF8 -Drhino.opt.level=9 -Djava.util.logging.manager=com.orientechnologies.common.log.ShutdownLogManager -Djava.util.logging.config.file=/home/ec2-user/owl/orientdb/config/orientdb-server-log.properties -Dorientdb.config.file=/home/ec2-user/owl/orientdb/config/orientdb-server-config.xml -Dorientdb.www.path=/home/ec2-user/owl/orientdb/www -Dorientdb.build.number=develop@rd31da1499f29f04af751d0a8ad108152b2593c8b; 2018-05-18 19:20:24+0000 -cp /home/ec2-user/owl/orientdb/lib/orientdb-server-3.0.1.jar:/home/ec2-user/owl/orientdb/lib/*:/home/ec2-user/owl/orientdb/plugins/* com.orientechnologies.orient.server.OServerMain ec2-user 28995 28993 0 18:26 pts/0 00:00:00 grep --color=auto -i 19169

ec2-user 20046 1 4 17:44 pts/0 00:01:46 /home/ec2-user/jdk1.8.0_131/bin/java -jar /home/ec2-user/owl/bin/owl-web-2.0.0.jar --server.port=9002 ec2-user 29003 29001 0 18:26 pts/0 00:00:00 grep --color=auto -i 20046

Notice the highlighted text above. Each component started via the owlmanage.sh script will start a java process for Orient, and the Owl-web application. These are the Pids owl will manage and keep track of. If for whatever reason these processes are not running it will be best to troubleshoot each component located in <INSTALL_PATH>/<COMPONENT>/log directory (where <COMPONENT> could be orient, hbase, etc) and look at the latest logs to determine why the process is not staying in the running state.

Another command an administrator can execute is the

jps

command, output as follows.

19169 OServerMain

3305 Jps

19309 ZeppelinServer

20046 owl-web-2.0.0.jar

The above output translates to the below.

• OServerMain = OrientDB

• ZeppelinServer = Apache Zeppelin

• owl-web-2.0.0.jar = Owl Web Application

In scenarios where owl starts Zookeeper there will be another process defined also that would identify zookeeper.

ps is another popular command to use such as ps -aef | grep -i postgresain order to validate postgres is running (NOTE: Postgres does not show up in the jps command because postgres is complied in the C language and jps looks at java processes).