- Article Type: General
- Product: Aleph
- Product Version: 18.01
We have created a script to move the previous Primo tar file to another directory and then run the publish_06 job. It's in the task_list for ABC01 to run at 10:00, 13:00, 16:00, 19:00. It has run successfully and completely. Sporadically over the weekend we got some errors in the file, and now the last 2 runs from yesterday and the first run today all get the error.
The script is /ABC/scripts/primo_updates:
# Script Name: primo_updates
# Date: 3/19/08
# move files from previous run to another directory
mv /primo_publishing/PRIMO-FULL/tar/*.gz /primo_publishing/PRIMO-FULL/tar/updates
# run publish_06 to create file for primo
csh -f $aleph_proc/p_publish_06 ABC01,PRIMO-FULL,LAST-DATE,000000000,999999999,00000000,99999999,,/primo_publishing,Y,05,
The log file in alephe/scratch has this:
mv: No match.
aleph_tr: Command not found
Param Initialization Failure, Exiting !!!
Log files from yesterday's 13:00 does not have the mv error as there was a previous file but does have the other errors. Where is the aleph_tr command coming from and what is the problem with it?
We have decided to move the job to the alephcr instead of the job_list.
Our testing showed that every time the job_list was reloaded from a captive account (which has group/owner ID of aleph:aleph) it caused the job to not run.
Reloading the job_list from a non-captive account resolved the problem.
- Article last edited: 10/8/2013