Changes between Version 13 and Version 14 of HetProcedures/RA/monitors

Timestamp:

Dec 22, 2018 10:19:41 AM (5 years ago)

Author:

shetrone

Comment:

--

HetProcedures/RA/monitors

@@ -14 +14 @@
 == Log files ==
 
-Perhaps more useful than the db are the log files.   These can be accessed during the night and include the current night a usually about a month of order logs.   They are located on the machine htcs which can be accessed as guider.    The logs are split into the different sub-systems: legacy, pfip, pas, tcs, and tracker.  They can be found in /var/log/tcs_logs/subsystem. There are several ways one might use these.  Note that to run this command you must be logged into htcs (e.g. ssh -X sco@htcs).
+Perhaps more useful than the db are the log files.   These can be accessed during the night and include the current night a usually about a month of order logs.   There are a number of different logs on different machines:
+  * TCS logs are located on htcs in /var/log/tcs_logs/subsystem_name/
+  * TCS_GUI logs are located on jove or mcs in /var/tcs_logs/
+  * VIRUS and LRS logs are located on vdas and lrs2 in /var/log/tcs_logs/instrument_name/
+  * Htopx logs are located in /data1/nossy/www/html/noss/htopx3/log/htopx.log
+
+
+The TCS logs are split into the different sub-systems: legacy, pfip, pas, tcs, and tracker.   There are several ways one might use these.  Note that to run this command you must be logged into htcs (e.g. ssh -X sco@htcs).
 
    * For example to look at the pfip probe motions to check for the "move complete" before making any further moves.   This would be done as {{{tail -F tcs_server.log | grep pfip}}}
    * One can also look for a "go_next" or "load_trajectory" inside of the tcs_server logs.
-   * Be sure to be looged into htcs.
+   * Be sure to be logged into htcs.
 
-
+One could look at the TCS GUI logs to see what buttons were pushed to get an idea if a problem was a human error or a software problem.   The htopx_logs are useful for looking to see when/if targets were incremented.
 
 == Nightly Databases ==
@@ -41 +48 @@
 {{{monitor --verbose -T --source-filter 'WFS*|DMI' --key-filter measurement }}}
 
+== working with the htopx and night report databases ==
 
+It is useful to know what fields can be queried with a mysql query in these databases.   To get a list try:  {{{ esql htopx -e "describe fullqueue"  }}}
+
+