You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am on a RHEL7 Linux box, using duck-7.7.1.33788-1.x86_64, with the Black Pearl Plugin.
I am able to use duck to list the contents of my Black Pearl
[app@curate-test1 ~]$ duck -u xxxxxxxxxxxx -p xxxxxxxxxx -v -l spectralogic-https://10.255.10.105/curatend-staging
Authenticating as Y3VyYXRlbmRfc3RhZ2luZw==…
The certificate for this server is invalid. You might be connecting to a server that is pretending to be 10.255.10.105 which could put your confidential information at risk. Would you like to connect to the server anyway? (y/n): y
> GET / HTTP/1.1
> HOST: 10.255.10.105:443
> DATE: Thu, 10 Dec 2020 18:57:32 +0000
> Content-Type: application/xml
> User-Agent: Cyberduck/7.7.1.33788 (Linux/3.10.0-1127.19.1.el7.x86_64) (amd64)
> Naming-Convention: s3
> Authorization: ********
> Connection: Keep-Alive
< HTTP/1.1 200 OK
< RequestHandler-Version: 1.8D18E6B210A254D12ACD074CF265700F
< x-amz-request-id: 473149
< Content-Type: text/xml;charset=UTF-8
< Content-Language: en-US
< Content-Length: 270
Login successful…
> GET /curatend-staging?delimiter=/&max_keys=1000&prefix&versions HTTP/1.1
> HOST: 10.255.10.105:443
> DATE: Thu, 10 Dec 2020 18:57:35 +0000
> Content-Type: application/xml
> User-Agent: Cyberduck/7.7.1.33788 (Linux/3.10.0-1127.19.1.el7.x86_64) (amd64)
> Naming-Convention: s3
> Authorization: ********
> Connection: Keep-Alive
< HTTP/1.1 200 OK
< RequestHandler-Version: 1.032AD615FE7006F89222B5D50F080D6A
< x-amz-request-id: 473150
< Content-Type: text/xml;charset=UTF-8
< Content-Language: en-US
< Content-Length: 292
< Date: Thu, 10 Dec 2020 18:57:35 GMT
**curate-test1**
However, if I try to create a remote directory, or upload a file, I am told that I am expecting md5 Checksums, but the system is providing SHA-512
[app@curate-test1 curatend]$ duck -u xxxxxxxxxxxxx -p xxxxxxxxx -v --upload spectralogic-https://10.255.10.105/curatend-staging/curate-test1/resque-pool-info /home/app/curatend/resque-pool-info
Authenticating as Y3VyYXRlbmRfc3RhZ2luZw==…
The certificate for this server is invalid. You might be connecting to a server that is pretending to be 10.255.10.105 which could put your confidential information at risk. Would you like to connect to the server anyway? (y/n): y
> GET /curatend-staging?delimiter=/&max_keys=1000&prefix=curate-test1/&versions HTTP/1.1
> HOST: 10.255.10.105:443
> DATE: Thu, 10 Dec 2020 19:09:11 +0000
> Content-Type: application/xml
> User-Agent: Cyberduck/7.7.1.33788 (Linux/3.10.0-1127.19.1.el7.x86_64) (amd64)
> Naming-Convention: s3
> Authorization: ********
> Connection: Keep-Alive
< HTTP/1.1 200 OK
< RequestHandler-Version: 1.032AD615FE7006F89222B5D50F080D6A
< x-amz-request-id: 473212
< Content-Type: text/xml;charset=UTF-8
< Content-Language: en-US
< Content-Length: 703
Login successful…
> GET /curatend-staging?delimiter=/&max_keys=1000&prefix=curate-test1/&versions HTTP/1.1
> HOST: 10.255.10.105:443
> DATE: Thu, 10 Dec 2020 19:09:15 +0000
> Content-Type: application/xml
> User-Agent: Cyberduck/7.7.1.33788 (Linux/3.10.0-1127.19.1.el7.x86_64) (amd64)
> Naming-Convention: s3
> Authorization: ********
> Connection: Keep-Alive
< HTTP/1.1 200 OK
< RequestHandler-Version: 1.032AD615FE7006F89222B5D50F080D6A
< x-amz-request-id: 473213
< Content-Type: text/xml;charset=UTF-8
< Content-Language: en-US
< Content-Length: 703
Prepare resque-pool-info (Overwrite)…
> PUT /_rest_/bucket/curatend-staging?max_upload_size=9223372036854775807&operation=start_bulk_put HTTP/1.1
> HOST: 10.255.10.105:443
> DATE: Thu, 10 Dec 2020 19:09:15 +0000
> Content-Type: application/xml
> User-Agent: Cyberduck/7.7.1.33788 (Linux/3.10.0-1127.19.1.el7.x86_64) (amd64)
> Naming-Convention: s3
> Authorization: ********
> Content-Length: 75
> Connection: Keep-Alive
< HTTP/1.1 200 OK
< RequestHandler-Version: 13.333A1A469EA035526C212DBBE3D17D8D
< x-amz-request-id: 473214
< Content-Type: text/xml;charset=UTF-8
< Content-Language: en-US
< Content-Length: 879
Uploading resque-pool-info…
> GET /_rest_/job_chunk?job=c6f9c246-e5a4-4bb0-8cb4-1094179e1f4b&preferred_number_of_chunks=2147483647 HTTP/1.1
> HOST: 10.255.10.105:443
> DATE: Thu, 10 Dec 2020 19:09:15 +0000
> Content-Type: application/xml
> User-Agent: Cyberduck/7.7.1.33788 (Linux/3.10.0-1127.19.1.el7.x86_64) (amd64)
> Naming-Convention: s3
> Authorization: ********
> Connection: Keep-Alive
< HTTP/1.1 200 OK
< RequestHandler-Version: 12.E85F3447509D8658DC4747BDBC1124AE
< Retry-After: 300
< x-amz-request-id: 473215
< Content-Type: text/xml;charset=UTF-8
< Content-Language: en-US
< Content-Length: 879
< Date: Thu, 10 Dec 2020 19:09:15 GMT
> PUT /curatend-staging/curate-test1/resque-pool-info?job=c6f9c246-e5a4-4bb0-8cb4-1094179e1f4b&offset=0 HTTP/1.1
> Date: Thu, 10 Dec 2020 19:09:15 GMT
> Expect: 100-continue
> Content-MD5: YqMf+cOIukHTHNZdNdIY8w==
> Content-Type: application/octet-stream
> Authorization: ********
> Content-Length: 68
> Host: 10.255.10.105:443
> Connection: Keep-Alive
[▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮▮] 68 B of 68 B (100%, 266 B/sec)
< HTTP/1.1 400 Bad Request
< RequestHandler-Version: 1.5B99BA64EAFD43AEC9359E716A93B234
< x-amz-request-id: 473216
< Content-Type: text/xml;charset=UTF-8
< Content-Language: en-US
< Content-Length: 276
< Date: Thu, 10 Dec 2020 19:09:15 GMT
Upload resque-pool-info failed. BadRequest[400]: CRCs for this bucket must be of type SHA-512. You transmitted a MD5. Please contact your web hosting service provider for assistance.
The black pearl is using SHA-512. This there a way for me to configure this?
The text was updated successfully, but these errors were encountered:
I am on a RHEL7 Linux box, using duck-7.7.1.33788-1.x86_64, with the Black Pearl Plugin.
I am able to use duck to list the contents of my Black Pearl
However, if I try to create a remote directory, or upload a file, I am told that I am expecting md5 Checksums, but the system is providing SHA-512
The black pearl is using SHA-512. This there a way for me to configure this?
The text was updated successfully, but these errors were encountered: