On successful backup duplicity exits with status 1

Bug #1691508 reported by Emmanuele Massimi on 2017-05-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Medium
Unassigned

Bug Description

Hi,

Duplicity: 0.7.12
OS: CentOS 5
Python: 2.6.8

I have set up duplicity to clear old files after it runs successfully, however I have noticed that even though the output doesn't show any errors, the exit status is always 1. Here is some sample output from my script (which basically reports the duplicity output and the exit status):

--- BEGIN ---

Reading globbing filelist /root/.duplicity/filelist.txt
Local and Remote metadata are synchronized, no sync needed.
Last full backup date: Sun May 7 06:37:20 2017
--------------[ Backup Statistics ]--------------
StartTime 1494998734.76 (Wed May 17 05:25:34 2017)
EndTime 1495005102.95 (Wed May 17 07:11:42 2017)
ElapsedTime 6368.19 (1 hour 46 minutes 8.19 seconds)
SourceFiles 2641072
SourceFileSize 5275317088344 (4.80 TB)
NewFiles 6
NewFileSize 98422 (96.1 KB)
DeletedFiles 0
ChangedFiles 12
ChangedFileSize 1381905357 (1.29 GB)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 18
RawDeltaSize 196055937 (187 MB)
TotalDestinationSizeChange 193748334 (185 MB)
Errors 0
-------------------------------------------------

Exit status: 1

--- END ---

As you can see, there are 0 reported errors, however the exit status is still 1. Due to this, old files are never actually removed, and I need to do that operation manually. This doesn't look like the intended behaviour, hence I'm reporting this as a bug.

Thank you for you time.

Download full text (3.5 KiB)

What is the command line?

On Wed, May 17, 2017 at 11:14 AM, Emmanuele Massimi <email address hidden>
wrote:

> Public bug reported:
>
> Hi,
>
> Duplicity: 0.7.12
> OS: CentOS 5
> Python: 2.6.8
>
> I have set up duplicity to clear old files after it runs successfully,
> however I have noticed that even though the output doesn't show any
> errors, the exit status is always 1. Here is some sample output from my
> script (which basically reports the duplicity output and the exit
> status):
>
> --- BEGIN ---
>
> Reading globbing filelist /root/.duplicity/filelist.txt
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Sun May 7 06:37:20 2017
> --------------[ Backup Statistics ]--------------
> StartTime 1494998734.76 (Wed May 17 05:25:34 2017)
> EndTime 1495005102.95 (Wed May 17 07:11:42 2017)
> ElapsedTime 6368.19 (1 hour 46 minutes 8.19 seconds)
> SourceFiles 2641072
> SourceFileSize 5275317088344 (4.80 TB)
> NewFiles 6
> NewFileSize 98422 (96.1 KB)
> DeletedFiles 0
> ChangedFiles 12
> ChangedFileSize 1381905357 (1.29 GB)
> ChangedDeltaSize 0 (0 bytes)
> DeltaEntries 18
> RawDeltaSize 196055937 (187 MB)
> TotalDestinationSizeChange 193748334 (185 MB)
> Errors 0
> -------------------------------------------------
>
> Exit status: 1
>
> --- END ---
>
> As you can see, there are 0 reported errors, however the exit status is
> still 1. Due to this, old files are never actually removed, and I need
> to do that operation manually. This doesn't look like the intended
> behaviour, hence I'm reporting this as a bug.
>
> Thank you for you time.
>
> ** Affects: duplicity
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1691508
>
> Title:
> On successful backup duplicity exits with status 1
>
> Status in Duplicity:
> New
>
> Bug description:
> Hi,
>
> Duplicity: 0.7.12
> OS: CentOS 5
> Python: 2.6.8
>
> I have set up duplicity to clear old files after it runs successfully,
> however I have noticed that even though the output doesn't show any
> errors, the exit status is always 1. Here is some sample output from
> my script (which basically reports the duplicity output and the exit
> status):
>
> --- BEGIN ---
>
> Reading globbing filelist /root/.duplicity/filelist.txt
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup date: Sun May 7 06:37:20 2017
> --------------[ Backup Statistics ]--------------
> StartTime 1494998734.76 (Wed May 17 05:25:34 2017)
> EndTime 1495005102.95 (Wed May 17 07:11:42 2017)
> ElapsedTime 6368.19 (1 hour 46 minutes 8.19 seconds)
> SourceFiles 2641072
> SourceFileSize 5275317088344 (4.80 TB)
> NewFiles 6
> NewFileSize 98422 (96.1 KB)
> DeletedFiles 0
> ChangedFiles 12
> ChangedFileSize 1381905357 (1.29 GB)
> ChangedDeltaSize 0 (0 bytes)
> DeltaEntries 18
> RawDeltaSize 196055937 (187 MB)
> TotalDestinationSizeChange 193748334 (185 MB)
> Errors 0
> -------------------------------------------------
>
> Exit status: 1
>
> --- END ---
>
> As you can see, there are 0 reported err...

Read more...

Emmanuele Massimi (finferflu-b) wrote :

The command line is as follows:

duplicity \
    --timeout=50000 \
    --no-encryption \
    --verbosity notice \
    --archive-dir=/home/.cache/duplicity \
    --tempdir=/home/.tmp/duplicity \
    --include-filelist /root/.duplicity/filelist.txt \
    --log-file /root/.duplicity/notice.log

What schema do you use? You left out the source and target on the command line.

Emmanuele Massimi (finferflu-b) wrote :

Oops, sorry about that, here's the full command:

duplicity \
    --timeout=50000 \
    --no-encryption \
    --verbosity notice \
    --archive-dir=/home/.cache/duplicity \
    --tempdir=/home/.tmp/duplicity \
    --include-filelist /root/.duplicity/filelist.txt \
    --log-file /root/.duplicity/notice.log \
    --full-if-older-than 30D \
    --asynchronous-upload \
    --gpg-options '-z 3' \
    --volsize=750 \
    / /home

Emmanuele Massimi (finferflu-b) wrote :

Would you be able to tell me whether this issue has been confirmed? Thank you very much!

No, not confirmed yet.

Would you look to see if any errors were logged? Perhaps attach it?

Does your include filelist include /dev or /proc? Willing to attach it?

Emmanuele Massimi (finferflu-b) wrote :

Unfortunately, there is nothing relevant in my notice.log; all I've got is the error I've pasted in the original bug report.

As for the filelist.txt file:

+ /etc
+ /var/spool/cron
- /data/.tmp
- /data/.cache
- **cache/**
- **log/**
- **logs/**
- /data/home/www.domain.tld (there's a bunch of entries like that)
+ /data
- /home/user
+ /home
- **

Thanks again for your assistance.

I believe this is fixed in the trunk now.

Changed in duplicity:
importance: Undecided → Medium
milestone: none → 0.7.14
status: New → Fix Committed
Emmanuele Massimi (finferflu-b) wrote :

Thanks for that! I will confirm it is fixed once it is released.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers