Cache Invalid, retry (internally handled)

Bug #1711750 reported by Daniel Davidson on 2017-08-18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Déjà Dup

Bug Description

1. Distribution: Arch Linux

2. Version: deja-dup 34.3

3. /tmp/deja-dup.gsettings (note, some values are redacted):

org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic true
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'file'
org.gnome.DejaDup last-run '2017-08-18T13:48:47.816923Z'
org.gnome.DejaDup nag-check '2017-08-14T00:58:19.656476Z'
org.gnome.DejaDup prompt-check '2017-05-09T22:12:29.666550Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['[redacted]']
org.gnome.DejaDup exclude-list ['[redacted]']
org.gnome.DejaDup last-backup '2017-08-18T13:48:47.816923Z'
org.gnome.DejaDup periodic-period 1
org.gnome.DejaDup delete-after 182
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder '[redacted]'
org.gnome.DejaDup.OpenStack authurl ''
org.gnome.DejaDup.OpenStack tenant ''
org.gnome.DejaDup.OpenStack username ''
org.gnome.DejaDup.OpenStack container '[redacted]'
org.gnome.DejaDup.GCS id ''
org.gnome.DejaDup.GCS bucket ''
org.gnome.DejaDup.GCS folder 'archpad'
org.gnome.DejaDup.GDrive email ''
org.gnome.DejaDup.GDrive folder '/deja-dup/[redacted]'
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.Rackspace container '[redacted]'
org.gnome.DejaDup.File path 'sftp://[redacted]'
org.gnome.DejaDup.File short-name ''
org.gnome.DejaDup.File uuid ''
org.gnome.DejaDup.File icon ''
org.gnome.DejaDup.File relpath @ay []
org.gnome.DejaDup.File name ''
org.gnome.DejaDup.File type 'normal'

4. /tmp/deja-dup.log: I do not have a log of when the error occurred. The subsequent backup was successful and is attached.


I suspect this issue occurred due to a backup being interrupted when I closed my laptop lid, but I could be wrong. The next backup was successful and this is the attached log. I think the error message could be clearer.

This has just occurred to me on Ubuntu 17.04. My laptop was not put to sleep/closed during the backup. The backup was to an SSH site. I've been doing that for years and never received this error (to my knowledge).

Vej (vej) wrote :

@Christopher Barrington-Leigh: Did the next backup finish without failure?

Changed in deja-dup:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments