Error:No module named cryptography.hazmat.backends
Closed this issue · 2 comments
/root/scripts/duplicity-backup/duplicity-backup.sh -c /etc/duplicity-backup.conf -f
hostname: Host name lookup failure
BackendException: Could not initialize backend: No module named cryptography.hazmat.backends
BackendException: Could not initialize backend: No module named cryptography.hazmat.backends
duplicity version 0.6.22-3.el6
Hi, thanks for reposting your issue here, which helps documenting users problems.
I am in no way affiliated to duplicity, only to this bash wrapper. In your case, it looks like the issue is in duplicity itself and not in duplicity-backup.sh (which makes no use of python and thus couldn't produce the error messages you received), so I will close the issue. You may ask for help on the mailing list of duplicity (http://lists.nongnu.org/mailman/listinfo/duplicity-talk). I strongly suggest to try to get duplicity working (directly, meaning without this script) before using duplicity-backup.sh. If you can make duplicity work but not duplicity-backup.sh then feel free to reopen this issue 😉
Thanks for considering duplicity-backup.sh and I hope you'll find the solution to your problem!
hey zertin,
thanks for the reply ya i found the solution after reinstalling
the cryptography package i am able to run the script.
On Sun, Nov 20, 2016 at 5:40 AM, zertrin notifications@github.com wrote:
Hi, thanks for reposting your issue here, which helps documenting users
problems.I am in no way affiliated to duplicity, only to this bash wrapper. In your
case, it looks like the issue is in duplicity itself and not in
duplicity-backup.sh (which makes no use of python and thus couldn't produce
the error messages you received), so I will close the issue. You may ask
for help on the mailing list of duplicity (http://lists.nongnu.org/
mailman/listinfo/duplicity-talk). I strongly suggest to try to get
duplicity working (directly, meaning without this script) before using
duplicity-backup.sh. If you can make duplicity work but not
duplicity-backup.sh then feel free to reopen this issue 😉Thanks for considering duplicity-backup.sh and I hope you'll find the
solution to your problem!—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#149 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWbtKf2F5EMH8BhgmOqU0rHFVuQw4vgeks5q_5AEgaJpZM4K1LqT
.
Regards,
Pradeep.kns