Back up fails with just the error "Invalid argument"

[Rene Horn]

This might possibly be related to Bug #792763, but the error is different, and the error log is different too.

The back up runs the scan, but once it's going to start uploading, that's when it fails (and says "Backup failed"), and gives the cryptic error message, "Invalid argument."

I did run the following to get an error log:

    DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 200 > /tmp/deja-dup.log

and so I've attached the log for examination.

Description: Ubuntu 12.10
deja-dup 24.0-0ubuntu1
duplicity 0.6.19-0ubuntu2
org.gnome.DejaDup backend 'file'
org.gnome.DejaDup delete-after 7
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup last-backup '2012-10-30T01:52:27.856077Z'
org.gnome.DejaDup last-restore '2012-01-30T02:52:45.714279Z'
org.gnome.DejaDup last-run '2012-10-30T01:52:27.856077Z'
org.gnome.DejaDup nag-check ''
org.gnome.DejaDup periodic true
org.gnome.DejaDup periodic-period 1
org.gnome.DejaDup prompt-check '2011-11-10T16:13:50.880503Z'
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup welcomed true
org.gnome.DejaDup.File icon '. GThemedIcon drive-harddisk-ata drive-harddisk drive'
org.gnome.DejaDup.File name '160 GB Solid-State Disk: OS'
org.gnome.DejaDup.File path 'smb://thingstoshare@sharonathena/extrastorage/seriallain'
org.gnome.DejaDup.File relpath @ay []
org.gnome.DejaDup.File short-name 'OS'
org.gnome.DejaDup.File type 'normal'
org.gnome.DejaDup.File uuid '2BC5-1A80'
org.gnome.DejaDup.Rackspace container 'seriallain'
org.gnome.DejaDup.Rackspace username ''
org.gnome.DejaDup.S3 bucket ''
org.gnome.DejaDup.S3 folder 'seriallain'
org.gnome.DejaDup.S3 id ''
org.gnome.DejaDup.U1 folder '/deja-dup/seriallain'

[Gustavo Fernandez Bayon (fernandezgustavo)]

I do confirm this happens all the time in my Ubuntu 12.04 when doing automatic backups. If I execute a backup manually, everything runs smoothly, but every morning when I arrive I find the same message: "Invalid argument".

My deja-dup version is 22.0, and I am backing up to a SMB share on a NAS. The backup is encrypted. I am attaching a log from a succesful deja-dup run.

Does anybody know how to activate logging for the automated backups so I can see tomorrow the output of the failing execution? Do I have to define the DEJA_DUP_DEBUG=1 in a certain place?

Any hint or help will be much appreciated.

Gus

[Michael Terry (mterry)]

Is the server by any chance not available yet when you see this error? I see "invalid argument" if I try to back up but the server isn't up yet on the network.

[Rene Horn (the-rhorn)]

I haven't seen this bug come back in a long time. I actually forgot about it. I have a new NAS now, and forgot about this bug until I got the email about this update. I'd say we can just close it. I'm not sure if the new NAS solved it or from the updates between then and now.

[Michael Terry (mterry)]

OK, thanks for the reply, and sorry it took me so long to get to this one. :-/ I'll close this out.

If anyone sees this again, please open a new bug. Might be different cause these days and it's better to have a fresh report.

[Michael Terry (mterry)]

I did file a bug upstream about seeing this message when the SMB server isn't available: https://bugzilla.gnome.org/show_bug.cgi?id=787917

That very will might have been it...? Or something similar in 2012-era gvfs.