duplicity-team team mailing list archive

Thread
Date

Re: [Question #557374]: Using Swift backend, signatures and manifests are not segmented

To: duplicity-team@xxxxxxxxxxxxxxxxxxx
From: Doug <question557374@xxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 13 Mar 2017 22:18:35 -0000
Reply-to: question557374@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

Question #557374 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/557374

Doug gave more information on the question:
The duplicity swift  error message is below:

Attempt 1 failed. ClientException: Object PUT failed: https://api.cloud.catalyst.net.nz:8443/v1/AUTH_a5f867bc7e244b51b7531097b55e7c00/cat-prod-seafile.catalyst.net.nz-seafile.catalyst.net.nz/duplicity-full-signatures.20170305T133159Z.sigtar.gz 413 Request Entity Too Large  [first 60 chars of response] <html>^M
<head><title>413 Request Entity Too Large</title></h
Attempt 2 failed. ClientException: Object PUT failed: https://api.cloud.catalyst.net.nz:8443/v1/AUTH_a5f867bc7e244b51b7531097b55e7c00/cat-prod-seafile.catalyst.net.nz-seafile.catalyst.net.nz/duplicity-full-signatures.20170305T133159Z.sigtar.gz 413 Request Entity Too Large  [first 60 chars of response] <html>^M
<head><title>413 Request Entity Too Large</title></h
Giving up after 3 attempts. ClientException: Object PUT failed: https://api.cloud.catalyst.net.nz:8443/v1/AUTH_a5f867bc7e244b51b7531097b55e7c00/cat-prod-seafile.catalyst.net.nz-seafile.catalyst.net.nz/duplicity-full-signatures.20170305T133159Z.sigtar.gz 413 Request Entity Too Large  [first 60 chars of response] <html>^M
<head><title>413 Request Entity Too Large</title></h
Backup failed with rc = 50

-- 
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.