'''These steps must be followed if SiTech has been restarted,''' hence the numbering continues from the section above. There are now autoguider-related programmes on both lesedis2 and the Mookodi PC, so the process involves both PCs.
10. From ioserver1, open another terminal tab(terminal #3), log in to the Mookodi PC and run following commands:
ssh mookodi@mookodi.suth.saao.ac.za
systemctl start lodestar_source_extr.service
11. Open another terminal tab (terminal #4) on ioserver1 and log in to lesedis2. If the autoguider backend software was open when SiTech shutdown then it has probably hung and won't respond to the red EXIT button. We need to kill it:
ssh observer@lesedis2.suth.saao.ac.za
kill -9 xxxxx ''(where xxxxx is the process ID reported from the ps aux task - kill all such processes)''
12. Then start the autoguider backend software(still in terminal #4):
sudo xauth merge ~/.Xauthority
sudo ./main_prog -depth 24
13. Open another terminal tab (terminal #5) on ioserver1 and start the guider web server:
ssh observer@lesedis2.suth.saao.ac.za
gunicorn -k gevent 'app:create_app()' -b 0.0.0.0:5001
14. Go back to the terminal tab connected to the Mookodi PC mookodi and start the autoguider comms/catalogue services:
systemctl stop gaia_list.service
sudo systemctl stop Mookodi_source_extract
sudo systemctl start Mookodi_source_extract
exit ''(to log out of mookodi)''
exit ''(to close terminal #5)''
15. Test:
* Point a browser to http://lesedis2.suth.saao.ac.za:5000 to load the TCS. If it loads ok, '''close the browser''' so the observer can log in from elsewhere. If it fails, repeat step 7. If it still fails, start again from step 4.
* Point a browser to 10.2.2.32:5001 to load the autoguider. If it loads ok, '''close the browser''' so the observer can log in from elsewhere - '''there must never be more than one instance of the autoguider open'''. If it fails, start again from step 10.
== Stopping SiTech Software ==