== Stopping and Starting the LRS2/VDAS camra server, monitor, and pivot processes ==

=== Stopping the servers ===

You can stop the camra_server by running
  '''sudo service ldas stop'''
the monitor by running
  '''sudo service ldas_monitor stop'''
and pivot by running
  '''sudo service ldas_pivot stop'''

(use vdas, vdas_monitor, or vdas_pivot for the virus cameras)


=== Starting the servers ===

To restart the lrs2 (or vdas) server, monitor, or pivot:

log on to lrs2 as yourself; we all have ldap account on these machines

you can use 'chksys' to see if the server/monitor/pivot are running

you can restart the camra_server by running
  '''sudo service ldas restart'''
the monitor by running
  '''sudo service ldas_monitor restart'''
and pivot by running
  '''sudo service ldas_pivot restart'''

(use vdas, vdas_monitor, or vdas_pivot for the virus cameras)

the output from these commands should look like

{{{
jrf@lrs2 ~
$ sudo service ldas restart
[sudo] password for jrf:
Stopping LRS2 Data Acquisition System                      [FAILED]
Starting LRS2 Data Acquisition System                      [  OK  ]

jrf@lrs2 ~
$ sudo service ldas_monitor start
Starting LRS2 Data Acquisition System Monitor              [  OK  ]

jrf@lrs2 ~
$ sudo service ldas_pivot start
Starting LRS2 Data Pivot              [  OK  ]

jrf@lrs2 ~
$ chksys

hetdex   31323     1  1 03:53 ?        00:00:05 /home/hetdex/code/het/trunk/camra/camra_server -c /home/hetdex/code/het/trunk/camra/etc/ldas.conf
hetdex   31374     1  0 03:53 ?        00:00:00 python /home/hetdex/code/het/trunk/camra/testing/ldas_monitor_temperatures.py
hetdex    8564     1  0 Mar30 ?        00:00:40 /home/hetdex/code/het/trunk/proxy/tcs_proxy --proxy-route ipc:///tmp/ldas_pivot.ipc --proxy-command /home/hetdex/code/het/trunk/camra/testing/proxy-pivot-het-data.sh
}}}

=== Problem Solving ===

The logs for the these programs can be found in the directory /var/log on either the lrs2 or vdas computer.  The file name formats are ldas.log, ldas_monitor.log, or ldas_pivot.log and vdas.log, vdas_monitor.log, or vdas_oivot.log.