Unsupported Protocol Scheme Swift Stack

Help and Support
1

What is the problem you are having with rclone?

When trying to copy between Swift Stack and another object vendor I receive the following message on the source:

2022-09-12 09:48:45 ERROR : files/docker/registry/v2/blobs/sha256/07/0700517de2f7a652d3161b2bdaf89db52624189314afdccffe5f339804f78724: error reading source directory: Head "/gitlab-container-registry/files/docker/registry/v2/blobs/sha256/07/0700517de2f7a652d3161b2bdaf89db52624189314afdccffe5f339804f78724/data": unsupported protocol scheme ""

Not sure if there is a place to change the protocol if even I need too and the error is accurate.

Run the command 'rclone version' and share the full output of the command.

rclone v1.58.1

  • os/version: redhat 7.9 (64 bit)
  • os/kernel: 3.10.0-1160.66.1.el7.x86_64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.17.9
  • go/linking: static
  • go/tags: none

Which cloud storage system are you using? (eg Google Drive)

Swift Stack

The command you were trying to run (eg rclone copy /tmp remote:tmp)

Paste command here

rclone copyto swift-gitlab:gitlab-container --exclude "/segments/" minio:gitlab-registry --progress

The rclone config contents with secrets removed.

Paste config here

This I'm unable to provide from my work space and the work I do.

A log from the command with the -vv flag

Paste  log here
```2022/09/12 09:56:13 DEBUG : Creating backend with remote "minio:gitlab-registry"
2022-09-12 09:56:54 DEBUG : pacer: low level retry 1/10 (error HTTP Error: 401: 401 Unauthorized)
2022-09-12 09:56:54 DEBUG : pacer: Rate limited, increasing sleep to 10ms
2022-09-12 09:57:14 DEBUG : pacer: Reducing sleep to 0s
2022-09-12 09:57:38 DEBUG : pacer: low level retry 1/10 (error HTTP Error: 401: 401 Unauthorized)
2022-09-12 09:57:38 DEBUG : pacer: Rate limited, increasing sleep to 10ms
2022-09-12 09:57:38 DEBUG : pacer: Reducing sleep to 0s
2022-09-12 09:57:53 DEBUG : files/docker/registry/v2/blobs/sha256/07/0700517de2f7a652d3161b2bdaf89db52624189314afdccffe5f339804f78724/data: Returning empty Md5sum for swift large object
2022-09-12 09:57:53 DEBUG : files/docker/registry/v2/blobs/sha256/02/02026e2ab91f5a8e65c6d60896a1273895b16b50f2400ff34508fc7ab7ce0428/data: Returning empty Md5sum for swift large object
2022-09-12 09:57:53 DEBUG : files/docker/registry/v2/blobs/sha256/02/02026e2ab91f5a8e65c6d60896a1273895b16b50f2400ff34508fc7ab7ce0428/data: Returning empty Md5sum for swift large object
2022-09-12 09:57:53 INFO  : files/docker/registry/v2/blobs/sha256/02/02026e2ab91f5a8e65c6d60896a1273895b16b50f2400ff34508fc7ab7ce0428/data: Copied (new)
2022-09-12 09:57:55 DEBUG : files/docker/registry/v2/blobs/sha256/07/0700517de2f7a652d3161b2bdaf89db52624189314afdccffe5f339804f78724/data: Returning empty Md5sum for swift large object
2022-09-12 09:57:55 INFO  : files/docker/registry/v2/blobs/sha256/07/0700517de2f7a652d3161b2bdaf89db52624189314afdccffe5f339804f78724/data: Copied (new)
2022-09-12 09:57:59 ERROR : files/docker/registry/v2/blobs/sha256/06/0600affc51d9b9052a9b6e7a6b5aca5d1d325cddac7137c21e4f9946ed9ad8c3: error reading source directory: Get "/gitlab-container-registry?delimiter=%2F&format=json&limit=1000&prefix=files%2Fdocker%2Fregistry%2Fv2%2Fblobs%2Fsha256%2F06%2F0600affc51d9b9052a9b6e7a6b5aca5d1d325cddac7137c21e4f9946ed9ad8c3%2F": unsupported protocol scheme ""
2

This is likely due to a misconfiguration - I'd guess your endpoint is missing https://

post your config with secrets redacted if you can't figure it out.

3

I will try and change that now then and try again. That's an weasy change to make for me and test.

4

[swift-gitlab]
type = swift
env_auth = false
user =
key =
auth = http://swift.send.net/auth/v1.0
region = us-east-1
storage_url = http://swift.send.net/v1/AUTH_gitlab
auth_version = 1

5

We also don't use https since everything is internal and so the https:// just give me a no route to host error.

6

You shouldn't have to put the storage_url in if the auth server is working properly - try commenting it out.

v1.0 auth is a bit long in the tooth now also are you sure that is what is required?

This could be a problem with the destination also.

Try making rclone lsl work on the source and the destination.

If it fails, retry with rclone lsl -vv --dump bodies and post the result.

7

Yes, I need the storage URL because you can't get to the contanier without using the swift stack. That was something I fought earlier on and had me stumped untul I entered that information. Only then could I get to the container.

8

Just so we end on a informative note for this one and Nick absolutely thank you for your help here. The solution to clear the swift stack nodes errors was to reboot the proxy nodes sequentially and then the 401 error along with the other message went away.

Also if you are wondering you can either manually issue a "sudo reboot" on the swift stack proxy nodes or you can go into the Controller GUI ---- > Clusters ----- > Manage ----- > Restart Proxy Services On Swift Nodes.

Hopefully this will at least help someone else.

1 Like
9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.