Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Aleph
    Ex Libris Knowledge Center

    save-yyyy-mm-dd subdirectories in ./xxx50/print directory

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Problem Symptoms:
    Though notices to patrons are produced and can be seen in the ./xxx50/print directory, they are not printed and there is no save-yyyy-mm-dd directory to which they are moved.

    Cause:
    Notices can be printed either manually or by the print daemon. The save-yyyy-mm-dd directory is created by the print daemon.

    1. If the print daemon is not running on a particular day (or if the print file's Print ID doesn't match the print daemon's), the file will not be printed and no save-yyyy-mm-dd will be created for that day.

    2. If the print_daemon *is* running but notices are not printed, check the print daemon log to see if it indicates a problem.

    Resolution:
    1. ***Make sure that the print daemon is running at times when notices are to be printed*** -- or very shortly thereafter.

    2. Click on "[D] Print Daemon" in the left-hand tree and then select "View Log" on the far right.

    Additional Information

    Example: The following are seen in the .../xxx50/print directory:

    drwxr-xr-x 2 aleph exlibris 4096 Jan 14 07:52 save-2014-01-14/
    -rw-r--r-- 1 aleph exlibris 48396 Jan 14 09:00 first_overdue_notice.20140114.printer01
    -rw-r--r-- 1 aleph exlibris 172288 Jan 14 09:10 second_overdue_notice.20140114.printer01
    -rw-r--r-- 1 aleph exlibris 0 Jan 14 09:15 third_overdue_notice.20140114.printer01
    -rw-r--r-- 1 aleph exlibris 18480 Jan 14 09:20 fourth_overdue_notice.20140114.printer01
    -rw-r--r-- 1 aleph exlibris 0 Jan 15 09:00 first_overdue_notice.20140115.printer01
    -rw-r--r-- 1 aleph exlibris 18730 Jan 15 09:10 second_overdue_notice.20140115.printer01
    -rw-r--r-- 1 aleph exlibris 11211 Jan 15 09:15 third_overdue_notice.20140115.printer01
    -rw-r--r-- 1 aleph exlibris 0 Jan 15 09:20 fourth_overdue_notice.20140115.printer01
    -rw-r--r-- 1 aleph exlibris 11185 Jan 16 09:00 first_overdue_notice.20140116.printer01
    -rw-r--r-- 1 aleph exlibris 0 Jan 16 09:10 second_overdue_notice.20140116.printer01
    -rw-r--r-- 1 aleph exlibris 0 Jan 16 09:15 third_overdue_notice.20140116.printer01
    -rw-r--r-- 1 aleph exlibris 0 Jan 16 09:20 fourth_overdue_notice.20140116.printer01

    It seems that the print daemon was running at 07:52 on 2014-01-14 and was stopped sometime between then and 09:00, and that the files produced since then have not been printed (by the print daemon) and have not been moved to a save directory.

    See also Article 000001729 ("Determine if notices produced by a batch job and processed by the Print Daemon were emailed successfully.")

    • Article last edited: 1/30/2014