java.io.IOException: entry 'shared/.lock' closed at '0' before the '15' bytes specified in the header were written

Atlassian JIRA | Michael Heemskerk | 2 years ago
  1. 0

    The backup client reports the following error: {noformat} 2014-08-02 02:00:44,927 ERROR (53%) Error writing tar file entry: The process cannot access the file because another process has locked a portion of the file java.io.IOException: The process cannot access the file because another process has locked a portion of the file at java.io.FileInputStream.readBytes(Native Method) ~[na:1.7.0_60] at java.io.FileInputStream.read(FileInputStream.java:272) ~[na:1.7.0_60] ... 13 more frames available in the log file 2014-08-02 02:00:44,973 ERROR (53%) Failed to close tar file entry: entry 'shared/.lock' closed at '0' before the '15' bytes specified in the header were written java.io.IOException: entry 'shared/.lock' closed at '0' before the '15' bytes specified in the header were written at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.closeArchiveEntry(TarArchiveOutputStream.java:363) ~[commons-compress-1.5.jar:1.5] at com.atlassian.stash.internal.backup.client.extensions.TarExtensions.withEntry(TarExtensions.groovy:31) ~[stash-backup-core-1.3.0.jar:na] ... 9 more frames available in the log file {noformat} This .lock file is created and held by Stash itself to prevent multiple instances from running with this shared-home. The .lock file should have been excluded from the backup, but hasn't been included in the default excludes list. As a workaround, add the following line to your {{backup-config.properties}}: {noformat} stash.home.excludes=**/.lock {noformat}

    Atlassian JIRA | 2 years ago | Michael Heemskerk
    java.io.IOException: entry 'shared/.lock' closed at '0' before the '15' bytes specified in the header were written
  2. 0

    The backup client reports the following error: {noformat} 2014-08-02 02:00:44,927 ERROR (53%) Error writing tar file entry: The process cannot access the file because another process has locked a portion of the file java.io.IOException: The process cannot access the file because another process has locked a portion of the file at java.io.FileInputStream.readBytes(Native Method) ~[na:1.7.0_60] at java.io.FileInputStream.read(FileInputStream.java:272) ~[na:1.7.0_60] ... 13 more frames available in the log file 2014-08-02 02:00:44,973 ERROR (53%) Failed to close tar file entry: entry 'shared/.lock' closed at '0' before the '15' bytes specified in the header were written java.io.IOException: entry 'shared/.lock' closed at '0' before the '15' bytes specified in the header were written at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.closeArchiveEntry(TarArchiveOutputStream.java:363) ~[commons-compress-1.5.jar:1.5] at com.atlassian.stash.internal.backup.client.extensions.TarExtensions.withEntry(TarExtensions.groovy:31) ~[stash-backup-core-1.3.0.jar:na] ... 9 more frames available in the log file {noformat} This .lock file is created and held by Stash itself to prevent multiple instances from running with this shared-home. The .lock file should have been excluded from the backup, but hasn't been included in the default excludes list. As a workaround, add the following line to your {{backup-config.properties}}: {noformat} stash.home.excludes=**/.lock {noformat}

    Atlassian JIRA | 2 years ago | Michael Heemskerk
    java.io.IOException: entry 'shared/.lock' closed at '0' before the '15' bytes specified in the header were written
  3. 0

    Auto-update broken: Updating 0.9.6 to 0.9.7 fails

    GitHub | 5 months ago | nlmarco
    java.io.IOException: entry 'backup/co.codewizards.cloudstore.server-0.9.6.backup-ipzjduva.tar.gz' closed at '65814528' before the '65818758' bytes specified in the header were written
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Aggregating other (non test) results?

    Google Groups | 5 years ago | Greg Moncreaff
    org.jvnet.hudson.plugins.backup.BackupException: java.io.IOException: org.codehaus.plexus.archiver.ArchiverException: Problem creating TAR: entry closed at '125153' before the '125154' bytes specified in the header were written
  6. 0

    Error when restarting Alluxio Master

    Google Groups | 6 months ago | donakalz
    java.lang.RuntimeException: java.io.IOException: The checkpoint must be written and closed before writing entries.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.io.IOException

      entry 'shared/.lock' closed at '0' before the '15' bytes specified in the header were written

      at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.closeArchiveEntry()
    2. Apache Commons Compress
      TarArchiveOutputStream.closeArchiveEntry
      1. org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.closeArchiveEntry(TarArchiveOutputStream.java:363)[commons-compress-1.5.jar:1.5]
      1 frame
    3. com.atlassian.stash
      TarExtensions.withEntry
      1. com.atlassian.stash.internal.backup.client.extensions.TarExtensions.withEntry(TarExtensions.groovy:31)[stash-backup-core-1.3.0.jar:na]
      1 frame