duplicity Errors 199 at end backup

[Battant]

Hello,

I use duplicity to backup my file. However. I get always this message at end backup with Error 199

--------------[ Backup Statistics ]--------------
StartTime 1524741993.34 (Thu Apr 26 13:26:33 2018)
EndTime 1524746175.96 (Thu Apr 26 14:36:15 2018)
ElapsedTime 4182.62 (1 hour 9 minutes 42.62 seconds)
SourceFiles 3821570
SourceFileSize 191576839080 (178 GB)
NewFiles 2088902
NewFileSize 191562222070 (178 GB)
DeletedFiles 3
ChangedFiles 54
ChangedFileSize 1834439 (1.75 MB)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 2088959
RawDeltaSize 0 (0 bytes)
TotalDestinationSizeChange 0 (0 bytes)
Errors 199lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic

Step to reproduce :
1. Configure duplicity
2. Run a bakup.
Result
3. At end backup, you should get Error 199
-------------------------------------------------
uname -r
4.15.0-20-generic

My configuration :

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04 LTS
Release: 18.04
Codename: bionic

apt-cache policy duplicity
duplicity:
  Installed: 0.7.17-0ubuntu1
  Candidate: 0.7.17-0ubuntu1
  Version table:
 *** 0.7.17-0ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

apt-cache policy python
python:
  Installed: 2.7.15~rc1-1
  Candidate: 2.7.15~rc1-1
  Version table:
 *** 2.7.15~rc1-1 500
        500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

Could you help me please to fix this issues ?

Thanks by advance for your support

Best regards

Battant

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: duplicity 0.7.17-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 26 15:58:41 2018
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

[Kenneth Loafman (kenneth-loafman)]

That's saying that duplicity logged 199 errors. They should be present in the log before this summary. It most likely is IO retries, but you should check and let us know what you find.

[Battant (mparchet)]

Helli,

Where duplicity.log is stored ?

Is log accessible throw journalctl command ?

Thanks for your support

Best regards

Battant

[Kenneth Loafman (kenneth-loafman)]

The log should be in ~/.cache/deja-dup/.

If you need more detail, you may need to run "export DEJA_DUP_DEBUG=1" before running deja-dup from the command line. That will produce a detailed log. Look for any errors reported there.

I have marked your other bug reports as duplicate of this one. Please comment on this bug report only, and do not create new reports. The number of errors detected will vary with the backup, but it's all the same "bug".

[Battant (mparchet)]

Hello,

I have tried to purge my backup drive and I have try again so I get this error at end backup

StartTime 1528282406.66 (Wed Jun 6 12:53:26 2018)
EndTime 1528287510.04 (Wed Jun 6 14:18:30 2018)
ElapsedTime 5103.38 (1 hour 25 minutes 3.38 seconds)
SourceFiles 4084048
SourceFileSize 209847935054 (195 GB)
NewFiles 2242605
NewFileSize 209833125235 (195 GB)
DeletedFiles 3
ChangedFiles 54
ChangedFileSize 2031344 (1.94 MB)
ChangedDeltaSize 0 (0 bytes)
DeltaEntries 2242662
RawDeltaSize 0 (0 bytes)
TotalDestinationSizeChange 0 (0 bytes)
Errors 256
-------------------------------------------------

Releasing lockfile /home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile
Removing still remembered temporary file /tmp/duplicity-_jqMVA-tempdir/mkstemp-PAe8Cn-1
Releasing lockfile /home/username/.cache/deja-dup/078943ce1c0e98d4e44486ca87a6cdd8/lockfile

I tried to locking for a log file in /home/username/.cache/deja-dup/ but i fond oly this

~/.cache/deja-dup/b09f92f79ac7e9cc320daa89d5904c35$ ls -laR /home/mparchet/.cache/deja-dup/

ls -laR /home/mparchet/.cache/deja-dup/
/home/mparchet/.cache/deja-dup/:
total 16
drwxrwxr-x 4 username groupname 4096 juin 6 14:12 .
drwx------ 30 username groupname 4096 juin 5 16:37 ..
drwxrwxr-x 2 username groupname 4096 juin 6 14:16 b09f92f79ac7e9cc320daa89d5904c35
drwxrwxr-x 2 username groupname 4096 juin 6 12:50 metadata

/home/username/.cache/deja-dup/b09f92f79ac7e9cc320daa89d5904c35:
total 5205540
drwxrwxr-x 2 username groupname 4096 juin 6 14:16 .
drwxrwxr-x 4 username groupname 4096 juin 6 14:12 ..
-rw-rw-r-- 1 username groupname 189087402 juin 6 14:15 duplicity-full.20180220T210034Z.manifest
-rw------- 1 username groupname 614036 juin 6 16:40 duplicity-full.20180606T121246Z.manifest.part
-rw-rw-r-- 1 username grouname 1590935331 juin 6 14:14 duplicity-full-signatures.20180220T210034Z.sigtar.gz
-rw------- 1 username groupname 3232084992 juin 6 16:40 duplicity-full-signatures.20180606T121246Z.sigtar.part
-rw-rw-r-- 1 username groupname 11049 juin 6 14:15 duplicity-inc.20180220T210034Z.to.20180222T022648Z.manifest
-rw-rw-r-- 1 username groupname 5996717 juin 6 14:15 duplicity-inc.20180222T022648Z.to.20180223T222309Z.manifest
-rw-rw-r-- 1 username groupname 38700246 juin 6 14:15 duplicity-inc.20180223T222309Z.to.20180404T135405Z.manifest
-rw-rw-r-- 1 username groupname 17927 juin 6 14:15 duplicity-inc.20180404T135405Z.to.20180405T022755Z.manifest
-rw-rw-r-- 1 username groupname 154 juin 6 14:15 duplicity-inc.20180405T022755Z.to.20180414T195141Z.manifest
-rw-rw-r-- 1 username groupname 1766726 juin 6 14:15 duplicity-new-signatures.20180220T210034Z.to.20180222T022648Z.sigtar.gz
-rw-rw-r-- 1 username gropunme 67652260 juin 6 14:15 duplicity-new-signatures.20180222T022648Z.to.20180223T222309Z.sigtar.gz
-rw-rw-r-- 1 username groupname 158448447 juin 6 14:15 duplicity-new-signatures.20180223T222309Z.to.20180404T135405Z.sigtar.gz
-rw-rw-r-- 1 username groupname 6909462 juin 6 14:15 duplicity-new-signatures.20180404T135405Z.to.20180405T022755Z.sigtar.gz
-rw-rw-r-- 1 username gropname 38197318 juin 6 14:15 dup...

[Kenneth Loafman (kenneth-loafman)]

Try running it like this from a terminal:

$ DEJA_DUP_DEBUG=1 deja-dup &> /tmp/deja-dup.log

After it's done, there will be a large log file in /tmp/deja-dup.log. Please look for through it and notice which errors are happening. These were not fatal, just noticeable.

NOTE: In another terminal you can follow the output with:

$ tail -f /tmp/deja-dup.log

[Battant (mparchet)]

Hello,

I have delete some files from my backup hard drive and I tried again and I have no error

So I have this question.

1. On mac os, if your backup drive is full, timeMachie delete the old backups
2. On my mac, if you change the computer name, you can merge tow backup.

Questions

What's the commands to do the same think with duplicity or deja-dup ?

Thanks for your support

Best regards

Battant

[Kenneth Loafman (kenneth-loafman)]

Yes, read the man page and pay attention to the 'cleanup' and 'remove-*' commands. With
$ duplicity cleanup --force <target url>"
you can clean out any partial backups taking up room. With
$ duplicity remove-all-but-n-full 2 <target url>
you can remove all but the last two backup sets.

You should be able to tailor this to your backup disk size and backup plan.