Overdue and lost reports running but not putting data in print files

• Article Type: General
• Product: Aleph
• Product Version: 20

Description:
Our overdue and lost reports have had 0 byte file sizes for the last few days. I've also attempted to change the job_list, but the jobs that should be commented out are not running, and new jobs I've submitted are also not running. We've lost information on patrons who have overdue items and lost bills.

Resolution:
There's a problem with the job daemon. I find that you have *two* jobd processes running:

...>ps -ef | grep jobd
root 4828 1 0 Aug07 ? 00:00:00 /exlibris/aleph/a20_1/aleph/exe/jobd a20_1
aleph 29271 1 0 Sep30 pts/3 00:00:00 /exlibris/aleph/a20_1/aleph/exe/jobd a20_1

You will note that one has root as the owner. This is incorrect. I think what happened was that someone (incorrectly) started the job daemon while logged on as root.

I suggest that you do the following:

> util e/15/2 to kill the job daemon
> ps -ef | grep jobd to confirm that no jobd processes are running. If there are, use "kill" command to kill them.
> util e/15/1 to activate the job daemon. This will prevent any future occurrences of the problem.

I believe the problem is that p_cir_51 ran multiple times with the same parameters (because of the duplicate jobd's). When multiple p_cir_51 runs occur on the same day, the second run will overwrite the good output from the first run with empty output.

The "How To Re-Run p_cir_51" document (in the How To/Circulation on the Doc Portal) describes how to handle this situation. You would need to use Method 3B for the overdues, and either Method 4A or 4C for the Lost notices. 4A is simpler and safer. Be sure to do the backups.

• Article last edited: 10/8/2013