AttributeError: S3Connection instance has no attribute 'aws_secret_access_key'

[Vincenzo Di Somma]

After nearly two days of sending stuff to Amazon S3 the backup finished, I removed a file and I've tried to restore and that's what I get:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1239, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1232, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1118, in main
    action = commandline.ProcessCommandLine(sys.argv[1:])
  File "/usr/lib/python2.6/dist-packages/duplicity/commandline.py", line 908, in ProcessCommandLine
    backup, local_pathname = set_backend(args[0], args[1])
  File "/usr/lib/python2.6/dist-packages/duplicity/commandline.py", line 803, in set_backend
    globals.backend = backend.get_backend(bend)
  File "/usr/lib/python2.6/dist-packages/duplicity/backend.py", line 153, in get_backend
    return _backends[pu.scheme](pu)
  File "/usr/lib/python2.6/dist-packages/duplicity/backends/botobackend.py", line 105, in __init__
    self.conn = S3Connection()
  File "/usr/lib/pymodules/python2.6/boto/s3/connection.py", line 104, in __init__
    path=path)
  File "/usr/lib/pymodules/python2.6/boto/connection.py", line 184, in __init__
    self.hmac = hmac.new(self.aws_secret_access_key, digestmod=sha)
AttributeError: S3Connection instance has no attribute 'aws_secret_access_key'

[celil (celil)]

I can confirm that this bug also affects me.

[Michael Terry (mterry)]

Ken, does this look familiar to you?

[someone1 (prateek)]

I have been uploading/restoring from Amazon S3 with no issues. Are you sure your script is properly coded (upload your script and leave out the actual keys?)

[Izaak Broere (sjaak-broere)]

In my case this only occurs when you choose to restore to the original location, if I choose a different location it worked fine. Can the others that experience this problem confirm this too?

[Michael Terry (mterry)]

Izaak, sounds like you get this on a full restore. Cecil, and Vincenzo: Were you doing a full restore or a single file restore?

[Vincenzo Di Somma (vds)]

Michael, single file restore.

[Wayne (wadevoe)]

I experience the problem when restoring to a different location or via right click "Revert To Previous Version..." The back-ups seem ok, I can see them in S3.

[David Ingram (rdingram)]

I would like to add that I also receive this error when trying to restore. In my case it only works if I restore to a new empty directory. Restoring to the original directory produces the error.

[Steve Blamey (fedorus-deactivatedaccount)]

I experience this issue when attempting a restore to an original or alternative location. If I download the backup files from s3 locally and use duplicity from the command line, I am able to restore files.

[Michael Terry (mterry)]

This bug should have been fixed with version 16.1 (available in maverick-proposed or from the PPA). I fixed an issue with environment variables (like the S3 password) not being passed to duplicity.

Can anyone confirm/deny if that is the case? I will assume so it's fixed if I don't hear anything.

[Steve Blamey (fedorus-deactivatedaccount)]

I am running 17.2 from the Testing PPA, but I can confirm that this bug is now fixed for me.

[Kevin Grover (kevin.grover)]

Thanks. I downloaded 17.4, but I can't compile it: glib-compile-schemas not
found by ./configure and glib2-devel not in my repository list (but
libglib2-dev is already installed).

I wanted to back some stuff up BEFORE upgrading Linux. I guess I'll just
image the drive and upgrade. I'll play with other stuff later.

<gripe>This is my one large gripe with Linux: if installs are not trivial
(e.g. package from a repository), they are near impossible. I like to learn
things, but I'm sick of having to take days out of my schedule to learn
stuff _right now_ to make things work. It sometimes makes my yearn for the
old Windows days. After upgrading Linux, I have to manually re-install
all the extra packages I had installed.... Sorry. </gripe>

On Sun, Jan 9, 2011 at 07:19, Steve Blamey <email address hidden>wrote:

> I am running 17.2 from the Testing PPA, but I can confirm that this bug
> is now fixed for me.
>
> --
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (700525).
> https://bugs.launchpad.net/bugs/585282
>
> Title:
> AttributeError: S3Connection instance has no attribute
> 'aws_secret_access_key'
>
> Status in Déjà Dup:
> Incomplete
>
> Bug description:
> After nearly two days of sending stuff to Amazon S3 the backup finished, I
> removed a file and I've tried to restore and that's what I get:
>
> Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1239, in <module>
> with_tempdir(main)
> File "/usr/bin/duplicity", line 1232, in with_tempdir
> fn()
> File "/usr/bin/duplicity", line 1118, in main
> action = commandline.ProcessCommandLine(sys.argv[1:])
> File "/usr/lib/python2.6/dist-packages/duplicity/commandline.py", line
> 908, in ProcessCommandLine
> backup, local_pathname = set_backend(args[0], args[1])
> File "/usr/lib/python2.6/dist-packages/duplicity/commandline.py", line
> 803, in set_backend
> globals.backend = backend.get_backend(bend)
> File "/usr/lib/python2.6/dist-packages/duplicity/backend.py", line 153, in
> get_backend
> return _backends[pu.scheme](pu)
> File "/usr/lib/python2.6/dist-packages/duplicity/backends/botobackend.py",
> line 105, in __init__
> self.conn = S3Connection()
> File "/usr/lib/pymodules/python2.6/boto/s3/connection.py", line 104, in
> __init__
> path=path)
> File "/usr/lib/pymodules/python2.6/boto/connection.py", line 184, in
> __init__
> self.hmac = hmac.new(self.aws_secret_access_key, digestmod=sha)
> AttributeError: S3Connection instance has no attribute
> 'aws_secret_access_key'
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/deja-dup/+bug/585282/+subscribe
>

[Michael Terry (mterry)]

Marking Fix Released based on Steve's report that it is working now.