[Ftplicity-general] Bug/config change on Duply v1.10?
Brought to you by:
edso
From: Angel P. R. <an...@cu...> - 2015-08-03 06:14:02
|
Hi, I have been checking duply/duplicity for a few days and it all worked fine for me. My backups were being uploaded to an S3 bucket successfully. But today I updated duply to the latest version 1.10 and the backend authorization feature stopped working. Find the log message attached, but it basically states: NoAuthHandlerFound: No handler was ready to authenticate. 1 handlers were checked. ['HmacAuthV1Handler'] Check your credentials I downgraded to duply version 1.9.2 and it works fine. I wonder whether something has changed in 1.10 on the way credentials have to be specified for S3 backend. The configuration on the duply profile looks like this: TARGET='s3://s3-us-west-1.amazonaws.com/bucket-name' TARGET_USER='%aws_access_key_id%' TARGET_PASS='%aws_secret_access_key%' Thanks for your work. Duply/duplicity will help us a lot to simplify our current backup mechanism for MongoDB. -- * Angel Pena Ruiz* Techops Engineer M +61 404435600 www.cultureamp.com * "The Survey Platform for People & Culture"* |