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. Batch log in Task Manager yields "failed to read reply".

    Batch log in Task Manager yields "failed to read reply".

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

    Description:
    The batch log from the task manager in the GUI in ABC01 and ABC50 does not connect. We get "failed to read reply" error message. It is working in ABC10 and ABC60.

    Is there a maximum size of the file for the batch log to display in the Task Manager?

    Resolution:
    The following grep (in abc01 $data_files) shows that the ABC01 batch_log has over 77,000 jobs in it:

    ABC01-ALEPH>>grep -c ' end' batch_log
    77875

    I think it is too big (24 meg.) for Task Manager to handle.

    I suggest that you do this for abc01:

    > dlib abc01
    > df1
    > mv batch_log batch.log.previous
    > touch batch_log

    Initially, the log will be empty, but once you submit jobs they should show up there.

    Then, the same for abc50.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • batch_log data
      • Batch merge vs. GUI Cataloging merge
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 17.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