duplicity Errors 199 at end backup

Bug #1767122 reported by Battant on 2018-04-26
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Medium
Kenneth Loafman
Déjà Dup
Undecided
Unassigned
Python
New
Undecided
Unassigned
duplicity (Ubuntu)
Undecided
Unassigned

Bug Description

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)

Battant (mparchet) wrote :

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.

Changed in duplicity (Ubuntu):
status: New → Incomplete
status: Incomplete → New
Changed in duplicity:
status: New → Incomplete
importance: Undecided → Medium
assignee: nobody → Kenneth Loafman (kenneth-loafman)
milestone: none → 0.7.18
Battant (mparchet) wrote :

Helli,

Where duplicity.log is stored ?

Is log accessible throw journalctl command ?

Thanks for your support

Best regards

Battant

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

Duplicates of this bug

Other bug subscribers