CAOBS Does Not Start

After a change to or from remote observing, the following observer may have trouble starting CAOBS. This is because although the previous observer has exited CAOBS, the process caobs_task may still exist. To fix this, ring the previous observer and ask them to log out of the window, or identify and kill the process yourself as below:

To view processes:
XBONES$>$ps -ef | grep -i caobs
If CAOBS-related tasks exist, kill them using the unix kill command (see Appendix P), using the process id (pid) number that the above command gives.

Other reasons why CAOBS might not start are:

• CACOR has crashed (or is otherwise dead)
• The disk partition $ATCA_LOG disk is full, i.e., a log file can't be created.
• CAOBS has hung following an ACC crash.