Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph
    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. p_print_11 (URL Check) limit of 16384 bytes in output file

    p_print_11 (URL Check) limit of 16384 bytes in output file

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Aleph
    • Product Version: 19.01

    Description:
    One of our libraries LRL50 has been trying to run print-11 on our production server, and it stops with the following error:

    alephe/scratch/lrl50_p_print_11.00019:

    Checking: http://www.leg.state.mn.us/edocs/edocs.asp?oclcnumber=04418067
    Checking: http://www.leg.state.mn.us/edocs/edocs.asp?oclcnumber=4435681
    Checking: http://www.citizensleague.net/publications/reporSegmentation Fault (core dumped)
    Wrote Z100 record with rec-key: 000013326
    Load: /exlibris/aleph/u19_1/alephe/tab/tab100

    Some more testing:

    First run: I moved the record that it was choking on to the 3 position in the input file and tried to rerun it. It choked again when the the correction file reached the filesize of 16384.

    Then I copied the file to url2 and removed all lines but 99 and reran the job again. It finished correctly without erring.

    So it appears there is a limit on the size of the output file that is causing the problem and has nothing to do with the records themselves.

    Resolution:
    Ex Libris was unable to reproduce this problem on our server; p_print_11 produced a file larger than 16384 without any problem.

    Ex Libris staff analyzed as follows:

    It seems that this was caused by a problem in a perl module "Crypt::SSLeay" when trying to retrieve an https URL.
    We reinstalled the module on the customer site and it seems fine now.
    We will probably have more Solaris customers with a similar problem.

    See KB 16384-35138 for a related case, containing the commands to reinstall the Crypt::SSLeay.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • P_PRINT_10 Unable to find correct permission for Proc-Name
      • p_print_11 produces errors for all records checked
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 19.01
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved