Webdav Upload per Curl bricht ab
3 years ago
Ich versuche ein 5gb Backup per curl in die Cloud zu laden. Es kommt ein Fehler und die Datei ist nicht vorhanden oder leer.
curl -v -T backup_$(date +'%m_%Y').tar -u nutzer:pw https://magentacloud.de/remote.php/webdav/backup_$(date +'%m_%Y').tar
* Trying 80.158.22.59:443...
* TCP_NODELAY set
* Connected to magentacloud.de (80.158.22.59) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
* subject: C=DE; O=Deutsche Telekom AG; ST=Hessen; L=Darmstadt; CN=magentacloud.de
* start date: Dec 3 10:17:11 2021 GMT
* expire date: Dec 7 23:59:59 2022 GMT
* subjectAltName: host "magentacloud.de" matched cert's "magentacloud.de"
* issuer: C=DE; O=T-Systems International GmbH; OU=T-Systems Trust Center; ST=Nordrhein Westfalen; postalCode=57250; L=Netphen; street=Untere Industriestr. 20; CN=TeleSec ServerPass Class 2 CA
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Server auth using Basic with user '****@gmail.com'
* Using Stream ID: 1 (easy handle 0x55b1a2e8db80)
> PUT /remote.php/webdav/backup_12_2021.tar HTTP/2
> Host: magentacloud.de
> authorization: Basic
> user-agent: curl/7.68.0
> accept: */*
> content-length: 5201448960
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* We are completely uploaded and fine
< HTTP/2 500
< date: Tue, 21 Dec 2021 16:40:56 GMT
< content-type: application/xml; charset=utf-8
< expires: Thu, 19 Nov 1981 08:52:00 GMT
< cache-control: no-store, no-cache, must-revalidate
< pragma: no-cache
< set-cookie: oc_sessionPassphrase=***; path=/; secure; HttpOnly; SameSite=Lax
< set-cookie: __Host-nc_sameSiteCookielax=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=lax
< set-cookie: __Host-nc_sameSiteCookiestrict=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=strict
< content-security-policy: default-src 'none';
< set-cookie: *****; path=/; secure; HttpOnly; SameSite=Lax
< strict-transport-security: max-age=15768000; includeSubDomains; preload;
< referrer-policy: no-referrer
< x-content-type-options: nosniff
< x-download-options: noopen
< x-frame-options: SAMEORIGIN
< x-permitted-cross-domain-policies: none
< x-robots-tag: none
< x-xss-protection: 1; mode=block
< server: elb
<
<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:exception>Sabre\DAV\Exception</s:exception>
<s:message>An exception occurred while uploading parts to a multipart upload. The following parts had errors:
- Part 2: Error executing "UploadPart" on "https://obs.eu-de.otc.t-systems.com/nmcloud-prod1-docs/urn***?partNumber=2&uploadId=***"; AWS HTTP error: Client error: `PUT https://obs.eu-de.otc.t-systems.com/nmcloud-prod1-docs/urn***?partNumber=2&uploadId=***` resulted in a `408 Request Timeout` response:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><Error><Code>RequestTimeout</Code><Message>The server did not rec (truncated...)
RequestTimeout (client): The server did not receive a complete request message within the time that it was prepared to wait. - <?xml version="1.0" encoding="UTF-8" standalone="yes"?><Error><Code>RequestTimeout</Code><Message>The server did not receive a complete request message within the time that it was prepared to wait.</Message><RequestId>***</RequestId><HostId>****</HostId></Error>
- Part 3: Error executing "UploadPart" on "https://obs.eu-de.otc.t-systems.com/nmcloud-prod1-docs/urn***?partNumber=3&uploadId=***"; AWS HTTP error: Client error: `PUT https://obs.eu-de.otc.t-systems.com/nmcloud-prod1-docs/***?partNumber=3&uploadId=***` resulted in a `408 Request Timeout` response:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><Error><Code>RequestTimeout</Code><Message>The server did not rec (truncated...)
RequestTimeout (client): The server did not receive a complete request message within the time that it was prepared to wait. - <?xml version="1.0" encoding="UTF-8" standalone="yes"?><Error><Code>RequestTimeout</Code><Message>The server did not receive a complete request message within the time that it was prepared to wait.</Message><RequestId>***</RequestId><HostId>****+phI</HostId></Error>
- Part 4: Error executing "UploadPart" on "https://obs.eu-de.otc.t-systems.com/nmcloud-prod1-docs/urn%3Aoid%***?partNumber=4&uploadId=***"; AWS HTTP error: Client error: `PUT https://obs.eu-de.otc.t-systems.com/nmcloud-prod1-docs/urn%3Aoid%***?partNumber=4&uploadId=***` resulted in a `408 Request Timeout` response:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><Error><Code>RequestTimeout</Code><Message>The server did not rec (truncated...)
RequestTimeout (client): The server did not receive a complete request message within the time that it was prepared to wait. - <?xml version="1.0" encoding="UTF-8" standalone="yes"?><Error><Code>RequestTimeout</Code><Message>The server did not receive a complete request message within the time that it was prepared to wait.</Message><RequestId>***</RequestId><HostId>***</HostId></Error>
- Part 5: Error executing "UploadPart" on "https://obs.eu-de.otc.t-systems.com/nmcloud-prod1-docs/urn%3Aoid%***?partNumber=5&uploadId=***"; AWS HTTP error: Client error: `PUT https://obs.eu-de.otc.t-systems.com/nmcloud-prod1-docs/urn%3Aoid%****?partNumber=5&uploadId=***` resulted in a `408 Request Timeout` response:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><Error><Code>RequestTimeout</Code><Message>The server did not rec (truncated...)
RequestTimeout (client): The server did not receive a complete request message within the time that it was prepared to wait. - <?xml version="1.0" encoding="UTF-8" standalone="yes"?><Error><Code>RequestTimeout</Code><Message>The server did not receive a complete request message within the time that it was prepared to wait.</Message><RequestId>***</RequestId><HostId>***</HostId></Error>
- Part 6: Error executing "UploadPart" on "https://obs.eu-de.otc.t-systems.com/nmcloud-prod1-docs/urn***?partNumber=6&uploadId=****"; AWS HTTP error: cURL error 35: OpenSSL SSL_connect: Broken pipe in connection to obs.eu-de.otc.t-systems.com:443 (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://obs.eu-de.otc.t-systems.com/nmcloud-prod1-docs/urn***?partNumber=6&uploadId=****
</s:message>
</d:error>
* Connection #0 to host magentacloud.de left intact
297
2
This could help you too
6 years ago
535
0
5
5 years ago
325
0
1
695
0
3
3 years ago
Hallo @Paschty
nachdem noch nicht einmal robocopy auf das WEBDAV-Lfw. funktioniert, glaube ich, dass hier noch erheblich nachgebessert werden muss. Bin mit der Umsetzung der Migration überhaupt nicht zufrieden.
Gruss -LERNI-
1
Answer
from
3 years ago
Gerade hat robocopy funktioniert... sehr seltsam
Unlogged in user
Answer
from
Unlogged in user
Ask
from