Backup jobs fails: Archives contains unclosed entries

Article ID:115001002007
1 minute readKnowledge base

Issue

The trace java.io.IOException: This archives contains unclosed entries, or java.io.IOException: No space left on device appears on the build console logs after running a backup job. You will also be able to find these traces in the Jenkins logs.

Environment

Resolution

Please review the following points:

  1. Backup job configuration: Build > Take backup > Where to back up? should be pointing to a different folder that Jenkins home folder ($JENKINS_HOME).

  2. CloudBees Backup Plugin >= 3.31 in order to get fixed JENKINS-20187.

In case the above points are met, the issue is not expected to happen and should be reported to CloudBees Support via ticket attaching the Support Bundle of the instance your a running the backup, plus the config.xml of the backup job.

Workarounds

In the meantime we review your particular case, there are several workarounds you could apply:

  1. Enable Build > Take backup > Skip recently modified files under the Advanced tab

    skipModifiedFiles

  2. Enable General Settings > Quiet period

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.