Changes
/* Starting Autoguider software */
'''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 in the terminal tab connected to lesedis2 (terminal #32), log in to the Mookodi PC and run following commands:
ssh observer@lesedis2.suth.saao.ac.za
systemctl start lodestar_source_extr.service
11. Open another terminal tab (terminal #43) 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 #43):
sudo xauth merge ~/.Xauthority
sudo ./main_prog -depth 24
13. Open another terminal tab (terminal #54) on ioserver1 and start the guider web server:
ssh observer@lesedis2.suth.saao.ac.za
If this step fails (symptom "Socket connected is False"), close the autoguider GUI and repeat steps 12 and 13.
14. Go back to the Open a final terminal tab connected (terminal #5) ssh to mookodi and start the autoguider comms/catalogue services:
ssh mookodi@mookodi.suth.saao.ac.za
systemctl stop gaia_list.service
systemctl start gaia_list.service
