Gtlab Restart

This document deals with restarting services on For the other servers, see Restarting Gtweb and Restarting gtoahpa

On gtoahpa, gtweb and gtlab, we use nginx for serving HTML and other applications. See how to restart nginx itself if needed (after an ordinary update is often is not).

Some Oahpa versions are on gtoahpa, others are on gtlab. To find them, write ls -l /home/|grep oahpa on the respective machines (or check the table below).

Current list (2016) on gtlab is bxr,crk,est,fkv,izh,liv,mdf,mhr,mrj,olo,udm,univ,vep,vro (names: bxr_oahpa, etc).

In case of emergencies...

The test versions of Oahpa (on

If all the Oahpa instances on gtlab are down (for example after server reboot) then you can start all the Oahpas at once, using the script

located in the directory


(requires sudo rights).

If an Oahpa on gtlab (e.g. gives "404 Not found" error then it means that nginx is running but the Oahpa (fastcgi) process has been stopped. For checking if the particular Oahpa process is running give the command:

    ps -ef | grep 'izh_oahpa'

If this command does not output 5-6 lines of fastcgi processes then you need to start the Oahpa process again. For doing that, go to the respective Oahpa's home directory, e.g.


and give the command (as sudo, if needed):

    sudo ./ --run

For making sure the Oahpas are online, you may click these links:

Oahpa-name URLs for the oahpa versions on gtlab

(The following Oahpas and Konteakstas are still listed on gtlab, but have been moved to gtoahpa: crk_oahpa, fkv_oahpa, sme Konteaksta (teaksta), univ_oahpa)

Restarting Nginx

Updates to the Oahpa code do not require restarting nginx, unless updating configuration files specifically for nginx. However, should the system reboot and nginx not survive this reboot, see how to restart nginx itself.

There have been problems with rebooting gtlab. If you after (re)starting nginx do not see the nginx test page when opening then try restarting iptables as well:

    sudo service iptables restart

If for some reason the system is running slowly, inspect processes running, using




, the latter of which is a more updated and easier to interpret tool.

Restarting Tomcat web server

This is where the instances of Konteaksta are running. After upgrade of the server, as well as adding new components to Konteaksta, it is always recommended to restart Tomcat. It is also the first thing to try if Konteaksta gives "server error". To restart Tomcat:

    sudo $CATALINA_HOME/bin/
    sudo $CATALINA_HOME/bin/

For compiling and redeploying Konteaksta (if needed):

    cd /home/teaksta
    svn up