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. Error: tar command failed in backup logs: "File changed as we read it"

    Error: tar command failed in backup logs: "File changed as we read it"

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1.  

     

    • Product: Aleph
    • Product Version: 20, 21, 22, 23
    • Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

     

     

    Problem Symptoms: 
    The ora_software backup uses tar to pack all relevant files into a compressed, split tar files 

    This Message at the end of the backup log files may indicate an error with backups: 

    "tar: Exiting with failure status due to previous errors 
    tar command failed {status=1}"
     

    After searching for these errors, (grep ^tar in relevant log file/s), you find the following: 
    "File changed as we read it" 

     

    Cause/Resolution: 
    This error is displayed when a file being handled by the tar process is changed / deleted during the tar action. 
    This is a warning that informs you that a file handled by the tar process might not be tar-ed. It does not actually mean that the backup has failed 

    If no application process (or Apache/PDS) is running during the backup you shouldn't worry about this warning. As long as you actually have a tar file of a similar size for the successful backup in the /exlibris/backup_file directory, there shouldn't be a problem. The file that is not being tarred is likely a non-essential log file. 

    If the error is in the prd_software log and the file is in the .../aleph.orig/.../tmp directory, this symbolic link from the .../aleph.orig/.../tmp to the active /tmp directory should be removed. (There is no need to back up tmp directory files as part of this Aleph software backup.)

     

    Additional Info
    See also Backup errors:in user_data_a5_Detail and prd_software_a4_Detail: "File removed before we read it"

     


    • Article last edited: 28-Feb-2016
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Error: PLAIN-ONLY is not allowed in $data_tab/tab100 of library ABC01
      • Error: write_xml_to_clob: ...unable to extend lob segment ...Z00P_SEGNAME by ...
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      This page has no tags.
    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