On successful backup duplicity exits with status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
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/.
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)
TotalDestinatio
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.
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
Changed in duplicity: | |
milestone: | 0.7.15 → 0.7.16 |
Changed in duplicity: | |
milestone: | 0.7.16 → none |
milestone: | none → 0.7.17 |
Changed in duplicity: | |
milestone: | 0.7.17 → none |
Changed in duplicity: | |
status: | In Progress → Fix Released |
assignee: | Kenneth Loafman (kenneth-loafman) → nobody |
What is the command line?
On Wed, May 17, 2017 at 11:14 AM, Emmanuele Massimi <email address hidden>
wrote:
> Public bug reported: duplicity/ filelist. txt nSizeChange 193748334 (185 MB) ------- ------- ------- ------- ------- ------- /bugs.launchpad .net/bugs/ 1691508 duplicity/ filelist. txt nSizeChange 193748334 (185 MB) ------- ------- ------- ------- ------- -------
>
> 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/.
> 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)
> TotalDestinatio
> 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:/
>
> 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/.
> 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)
> TotalDestinatio
> Errors 0
> -------
>
> Exit status: 1
>
> --- END ---
>
> As you can see, there are 0 reported err...