Runlog: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 5: | Line 5: | ||
'''run_log_end_update''' can be run after run is finished to recover database information in case of end run failure. It assumes that ascii files were restored by running ''run_log_recovery''. | '''run_log_end_update''' can be run after run is finished to recover database information in case of end run failure. It assumes that ascii files were restored by running ''run_log_recovery''. | ||
CRON job is running on clon10 to restore database in case if end of run failed. It starts script ''run_cleanup'', which it turn runs following commands: | CRON job is running every hour on clon10 to restore database in case if end of run failed. It starts script ''run_cleanup'', which it turn runs following commands: | ||
cd $CLON_PARMS/run_files | cd $CLON_PARMS/run_files | ||
run_log_files -a clasprod -s clasprod *.txt | run_log_files -a clasprod -s clasprod *.txt | ||
Revision as of 07:38, 30 May 2009
The number of programs located in $CLON/src/runlog and running at various stages of the Data Aquisition process.
run_log_recovery reprocess raw datafiles from raid disk(s) or /work/recovery directory and restores ascii files lost in case of end run failure.
run_log_end_update can be run after run is finished to recover database information in case of end run failure. It assumes that ascii files were restored by running run_log_recovery.
CRON job is running every hour on clon10 to restore database in case if end of run failed. It starts script run_cleanup, which it turn runs following commands:
cd $CLON_PARMS/run_files run_log_files -a clasprod -s clasprod *.txt run_log_end -a clasprod -s clasprod *.txt run_file_clean *.txt
Database got updated, new xml tags inserted into run_files, and after that run_files moved into archive subdirectory.