In case of emergencies...
This document deals with restarting httpd services on gtoahpa.uit.no,
On gtoahpa, gtweb and gtlab, we use nginx for serving HTML
Restarting the dictionaries on gtoahpa
Log in to gtoahpa, log in as neahtta, go to /home/neahtta/neahtta and issue:
fab sanit restart_service fab baakoeh restart_service
Restarting Oahpa versions on gtoahpa
Log in to gtoahpa.
Some Oahpa versions are on gtoahpa, others are on gtlab. To find which
NOTE:We are now in the process of moving most of these to gtoahpa-01. Contact Cip or Chiara on issues concerning these.
Oahpas on gtoahpa:
The following is the list of Oahpas on gtoahpa as of 28.11.2018:
|myv_oahpa||Erzya||oahpa.no/erzya||Should be online 3.-8.12.|
|udm_oahpa||Udmurt||oahpa.no/udm_oahpa||Restarted (note address)|
Oahpas on gtoahpa-01:
The folowing is the list of oahpas already moved to gtoahpa-01:
Restarting on the old gtoahpa:
Once an Oahpa version is down, it must be restarted.
sudo service OAHPANAME restart
where OAHPANAME is the relevant Oahpa version (crk_oahpa, fkv_oahpa etc).
If only an Oahpa version has been down, this is enough. If the server has been totally down, you may need to start more. Here is the full list of services that
For each of the processes listed, issue (anywhere on the system)
sudo service NAME restart
Thus, sudo service mysqld restart, etc.
After that, run all the Oahpa restarting commands:
sudo service crk_oahpa restart
Konteaksta is running on the Tomcat web server. After upgrade of gtoahpa, as well as adding new components to Konteaksta, it is always recommended to restart Konteaksta (the script compiles the Konteaksta source code, redeploys it on Tomcat and restarts Tomcat). Restarting Konteaksta is also the first thing to try if the url oahpa.no/konteaksta gives "server error", e.g. "The page you are looking for is temporarily unavailable. Please try again later.".
To restart Konteaksta:
Log in to gtoahpa and issue the command:
sudo service konteaksta restart
Restarting oahpas the hard way, without the service script
There is an init.d script for restarting each oahpa instance,
In case the sudo service etc. does not work, here is another option
Go to the catalogue /home/fkv_oahpa/fkv_oahpa
, which stores a PID to a file to halt
The system may return an error message, along the lines of
If running of the script results in error:
./run_fastcgi.sh: line 10: kill: (332) - Ingen slik prosess
then the process id saved in the file fastcgi.pid is wrong. In such a case you need to change the file. The command
ps -ef | grep 'fkv_oahpa'
gives you a list of all fastcgi processes related to fkv_oahpa. There should be 6 processes for each oahpa. Check the time when the first process was started (the process that generates the remaining 5 processes). Write the PID of the process into the file fastcgi.pid and run the script run_fastcgi.sh again.
PHP applications, Wordpress in our case, are managed by a global server process,
sudo service php-fpm restart