Permission Denied error during backup

Bug #851771 reported by Keith Drummond
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
deja-dup (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Deja Dup has been backing up as normal to an external HDD since I have been using 11.10 Beta1, but for the last 2 days I have been getting a permission denied error. I have not altered any settings and the extrenal HDD is performing as normal.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: deja-dup 19.92-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Fri Sep 16 11:54:40 2011
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Keith Drummond (kd353) wrote :
Revision history for this message
Keith Drummond (kd353) wrote :

From looking at a similar bug ( #847439) I see the problem there was with a SSH connection. I have tried running the command

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

but the file is empty and the same pop-up appears saying that permission is denied.

Revision history for this message
Keith Drummond (kd353) wrote :

Please mark as invalid, have just retried again and it seems to be working. Have just completed a backup.

Michael Terry (mterry)
Changed in deja-dup (Ubuntu):
status: New → Invalid
Revision history for this message
Blown2bits (blown2bits) wrote :

I have the same problem. When I check the number of files in the backup folder it is always 2,027. If anyone gets this issue, post the number of files in your backup folder.

I am using a 1.82 TB ext4 partition on a non-root drive connected to Sata III.

Changed in deja-dup (Ubuntu):
status: Invalid → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in deja-dup (Ubuntu):
status: New → Confirmed
Revision history for this message
David Arnstein (arnstein) wrote :

I launch the "Backup" panel from the Ubuntu Settings application. Then I perform a backup. After the backup completes, I get a pop-up window presenting a list of files that were not backed up. The list is extensive, and includes important looking files in /boot and so forth.

In a subsequent test, I launch deja-dup from "sudo." Then I do a backup, as above. This time, the backup job completes without any warnings or errors.

It seems to me that the integration of deja-dup into the Ubuntu Settings application needs to ask for a privileged password, and then launch deja-dup with high privilege.

Revision history for this message
Ruairi (ruhann) wrote :

I have had the same issue here, but I dont believe ths issue is with Deja-Dup.
In may case I physically chaged the back-up machine (192.168.0.99)

I log into the backup nachine with ssh and ftp

Duplicity provides and error:

duplicity full Travel/ sftp://sr@192.168.0.99/Backup/ideapad/
The authenticity of host '192.168.0.99' can't be established.
SSH-RSA key fingerprint is <<blah blah blah>>
Are you sure you want to continue connecting (yes/no)? yes
BackendException: ssh connection to sr@192.168.0.99:22 failed: No authentication methods available

ru@ru-460:~$ sudo duplicity full Travel/ sftp://sr@192.168.0.99/Backup/ideapad/
BackendException: ssh connection to sr@192.168.0.99:22 failed: No authentication methods available

Running Duplicity in verbose mode shows:
u@ru-460:~/.config$ duplicity -v 9 full Travel/ sftp://sr@192.168.0.99/Backup/ideapad/
Using archive dir: /home/ru/.cache/duplicity/7744528ccaaf2107c20395b1fa95181c
Using backup name: 7744528ccaaf2107c20395b1fa95181c
Import of duplicity.backends.u1backend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.ftpsbackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Import of duplicity.backends.ftpbackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.cloudfilesbackend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.sshbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Using temporary directory /tmp/duplicity-g16iDW-tempdir
Backend error detail: Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1404, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1397, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1248, in main
    action = commandline.ProcessCommandLine(sys.argv[1:])
  File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 1002, in ProcessCommandLine
    backup, local_pathname = set_backend(args[0], args[1])
  File "/usr/lib/python2.7/dist-packages/duplicity/commandline.py", line 895, in set_backend
    globals.backend = backend.get_backend(bend)
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 161, in get_backend
    return _backends[pu.scheme](pu)
  File "/usr/lib/python2.7/dist-packages/duplicity/backends/_ssh_paramiko.py", line 182, in __init__
    self.config['port'],e))
BackendException: ssh connection to sr@192.168.0.99:22 failed: No authentication methods available

BackendException: ssh connection to sr@192.168.0.99:22 failed: No authentication methods available

Meaning Deja-Dup -> Duplicity -> Paramiko

Revision history for this message
Ruairi (ruhann) wrote :

DejaDUP works for me now. just insert the full path into the DejaDUp GUI
Instead of "/Backup/ideapad" -> "/home/sr/Backup/ideapad"

Works a charm, the issue for me is that SSH logs one into the home folder by default, while Paramiko seem to log one into root.

The command line is giving me errors on both paths, ( I assume this is my error) but the GUI is fully operational

Revision history for this message
dino99 (9d9) wrote :

This version has expired

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.