-
Notifications
You must be signed in to change notification settings - Fork 4
Maintainer Guidelines: disaster recovery plan
All services are under control of monit. If there is need to manually start services: here is a how to.
(see how monit does it at root@quaoar1:~#/etc/monit/conf.d/play-instances.rc)
If manually starting does not help, you may want to restart the server (as root do: shutdown -r now. In worst case, call the IT so that they can pull the trigger and start the trigger again ). Normally everything will come up automatically. If there is a case like e.g. hard disk is full, you would have to search for big files which can be deleted: use df -h to identify the hard disk in question. Change to the root of the hard disk and run ncdu to identify big files and remove them if these are old log files.
First, login to the server: ssh sol@quaoar1 for production, ssh sol@quaoar2 for stage/fallback.
/home/sol/git/lobid-resources-alma/web/monit_restart.sh lobid-resources-alma/web start 7507 -Xmx12G,-Xms12G
Read https://github.com/hbz/lobid-resources/wiki/Maintaining-Alma.lobid-API for more background and hints.
/home/sol/git/lobid-gnd/monit_restart.sh lobid-gnd start 7100
/home/sol/git/lobid-resources/web/monit_restart.sh lobid-resources/web start 7500 -Xmx32768m,-Xms32768m
bash /home/sol/git/lobid-organisations/monit_restart.sh lobid-organisations start 7200 -Xms1024m,-Xmx8192m
/home/sol/git/nwbib/monit_restart.sh nwbib start 8000 -Xmx2048m,-Xms2048m
ssh lod@gaia
/bin/bash /etc/init.d/skohub-vocabs.sh start