DAQ/Online Quick Reference

DAQ Recovery Procedure

In most cases DAQ will crash because of ROC problem. Do following:

• click 'End Run' or 'Abort', whatever button is active

• click 'Cancel' and then 'Reset'

• go to 'EB_TERM' window, Ctrl-C and run previous command using arrow up (command is 'coda_eb ...')

• run 'roc_status' command from clon10 window; it will show troubled ROC(s) as 'UNDEFINED' or 'active'

• from clon10 window, reboot troubled ROC(s) using command 'roc_reboot <roc>'

• wait 2 minutes and run 'roc_status' again; rebooted ROC(s) must be in 'booted' stage

• start new run from 'Download'

If it does not help, page DAQ pager.

FOLLOWING INFORMATION IS FOR DAQ EXPERTS ONLY (DO NOT DO IT IF YOU ARE NOT SURE !!!)

DAQ procedures

First make sure you can open X window from the terminal clon03:0.1: type 'xterm' and make sure xterminal is opened. If it is not, message 'X11 connection rejected because of wrong authentication.' will shows up. In this case kill xwindow, start new one (you will be on clon03) and 'ssh clon10'. Make sure 'xterm' command can open xterminal.

To start all DAQ processes goto clon10 as clasrun and type

daq_start this

to open all windows on current workspace. If daq_start executed without parameter, it will open everything on clon03's bottom screen on currently active workspace.

To kill all DAQ processes goto clon10 as clasrun and type

daq_exit

Online procedures

To start online monitoring processes use following commands:

mon_start (starts everything on clon00 - root)
mon1_start (starts everything on clonmon1 - event_monitor)
mon2_start (starts everything on clon04 - recsis, ced)

they will start everything on clon00, clonmon1 and clon04 respectively.

To kill online monitoring processes use following commands:

mon_exit (kills everything on clon00)
mon1_exit (kills everything on clonmon1)
mon2_exit (kills everything on clon04)

Occupancy plots must be started on clonmon1. Login as clasrun and type

monb

Background information

• CRON JOBS: on clon10, clon00, clon01 and clondb1 make sure cron jobs are running (they must start automatically after reboot); if have to start cron jobs, login as clascron to the mentioned machines, goto directory /home/clascron/backup and follow instructions in README file, normally it will be following:

login as 'clascron' to the clon10
goto /home/clascron/backup
type 'crontab -l' to see what is running
type 'crontab -r' to erase all existing cron jobs
type 'crontab clon10'
repeat everything for clon00 and clon01, using file 'clon00' and 'clon01' respectively

Sometimes you may want to turn some cron jobs off to avoid alarms during system reconfiguration: do not forget to turn them on again after you are done !

• Process management: SmartSockets-based process management procedures must be started as clasrun using following command:

control_process_manager start clasprod clasprod
control_procmgr_manager start clasprod clasprod
control_ipc_process_manager start clasprod clasprod

and killed by following:

control_process_manager stop clasprod clasprod
control_procmgr_manager stop clasprod clasprod
control_ipc_process_manager stop clasprod clasprod

Sergey Boyarinov: Moscow cell phone: 011-7-916-729-8203