Re: [Duplicity-talk] duplicity cleanup not really cleaning up

[edgar . soldin]

On 17.05.2014 11:39, Luca Gibelli wrote:
> Hi,
> 
> at Skylable we use duplicity to backup our machines.
> 
> We follow the principle of eating our own dog food, so we store the backups 
> on a cluster running LibreS3, the open-source S3 solution that we just 
> released[1].
> 
> Yesterday we got an error from duplicity:
> 
> http://pastebin.com/mCwM77ML
> 
> The backup completed successfully, but look at this:
> 
> - - -
> Warning, found incomplete backup sets, probably left from aborted session
> Deleting these files from backend:
> [...]
> duplicity-new-signatures.20140421T030631Z.to.20140422T030719Z.sigtar.gpg
> [...]
> Download 
> s3://xxx:8443/skylablebackups/ethos//duplicity-new-signatures.20140421T030631Z.to.20140422T030719Z.sigtar.gpg
>  failed (attempt #1, reason: S3ResponseError: S3ResponseError: 404 Not Found
> [...]
> - - -
> 
> This server was rebooted ~30 days ago while duplicity was running, 
> so I'm not surprised that 'duplicity cleanup' is trying to delete the 
> incomplete backup.
> 
> What I don't understand is why, later on, duplicity expects the file to be 
> there.
> 
> I assume the cleanup process should have removed any traces of the 
> incomplete backups?
> 
> Versions:
> 
> $ duplicity -V
> duplicity 0.6.18
> $ python -c 'import boto; print boto.Version'
> 2.3.0
> 
> 

there were some fixes wrt. to deleting files in several backends.
update to 0.6.24 and see if the error persists. 

..ede/duply.net