Rclone stuck tardigrade

What is the problem you are having with rclone?

Is stuck forever when using command ls on tardigrade but in another VM works fine. I'm using Oracle Cloud services and never had this issue. Config is correct because I copy from rclone.conf. Other servers like mega work fine.

What is your rclone version (output from rclone version)

rclone v1.57.0-beta.5652.f7f4468cb

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

Tardigrade

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

rclone ls xxxx:xxxx

The rclone config contents with secrets removed.

[aaa]
type = tardigrade
satellite_address = aaa
api_key = aaa
passphrase = aaaa
access_grant = aaa

A log from the command with the -vv flag

rclone -vv ls storj1:storage1
2021/09/05 18:15:19 DEBUG : rclone: Version "v1.57.0-beta.5652.f7f4468cb" starting with parameters ["rclone" "-vv" "ls" "xxx:xxx"]
2021/09/05 18:15:19 DEBUG : Creating backend with remote "xxx:xxx"
2021/09/05 18:15:19 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2021/09/05 18:15:19 DEBUG : FS sj://storage1: connecting...
2021/09/05 18:15:19 DEBUG : FS sj://storage1: connected: <nil>
2021/09/05 18:15:19 DEBUG : FS sj://storage1: ls -R ./
2021/09/05 18:15:19 DEBUG : FS sj://storage1: OBJ ls -R ./ ("aaa", "")
*stuck here*

hello and welcome to the forum,

so you are running rclone on two different machine and on one machine you have a problem?
are both machines virtual on Oracle cloud?

can you post the full rclone version from both machine, should look like

rclone version
rclone v1.56.0
- os/version: ubuntu 21.04 (64 bit)
- os/kernel: 5.11.0-1016-raspi (aarch64)
- os/type: linux
- os/arch: arm64
- go/version: go1.16.5
- go/linking: static
- go/tags: none

You understood correctly. I tried the stable version in both VM first then beta, same issue.


rclone v1.57.0-beta.5652.f7f4468cb
- os/version: ubuntu 20.04 (64 bit)
- os/kernel: 5.11.0-1016-oracle (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.17
- go/linking: static
- go/tags: none

rclone v1.56.0
- os/version: ubuntu 20.04 (64 bit)
- os/kernel: 5.11.0-1016-oracle (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.16.5
- go/linking: static
- go/tags: none

i have never used tardigrade.
on other providers, these flags can give a more detailed debug log.
--dump=headers --retries=1 --low-level-retries=1 --log-level=DEBUG --log-file=rclone.log

on the vm with the problem, using tardigrade cli tool, have you tried ls , does it work?

Just tested uplink in both machines and it gets stuck and throws this code

Error: uplink: metaclient: rpc: dial tcp 34.89.57.123:7777: i/o timeout; unable to unmarshal access grant: proto: pb.Scope: illegal tag 0 (wire typ                             e 2)

The other machine works fine with uplink, same config.

the odds are there is something wrong with that machine, not related to rclone.

that error is from the rclone debug log?

can you post the full debug log, not just a one-line snippet.
or at least the top lines of the debug log...

No that error is from uplink cli. The rclone debug log is exactly the same as the command with the -vv flag which is already posted

makes sense, as it did not look like an rclone ERROR : format.

after you get that issue fixed, rclone should work....

When testing rclone -vv config

2021/09/05 20:13:37 DEBUG : Saving config "passphrase" in section "storj" of the config file
2021/09/05 20:13:37 DEBUG : Keeping previous permissions for config file: -rw-rw -r--
2021/09/05 20:13:37 DEBUG : storj: config out: out=&{State:*all,5,false Option:< nil> OAuth: Error: Result:}, err=
2021/09/05 20:13:37 DEBUG : storj: config in: state="*all,5,false", result=""
2021/09/05 20:13:37 DEBUG : storj: config out: out=&{State:*postconfig Option: OAuth: Error: Result:}, err=
2021/09/05 20:13:37 DEBUG : storj: config in: state="*postconfig", result=""
2021/09/05 20:13:37 DEBUG : storj: config in: state="", result=""

stuck here

so both machines throw the code and rclone works on one of them?

that debug log looks very different from the first log you posted.
in the second debug log, getting an OAuth error.

and please try to post complete debug log, not just a snippet.

Can you kill -QUIT the rclone process (or press CTRL-\) when it gets stuck and post the backtrace please? That will tell us where rclone is stuck. However I suspect it is getting stuck in the same place as uplink

This probably means it isn't rclone's problem if uplink doesn't work. Would you agree?

I would guess there is some kind of firewall in the way that is stopping the connections.

This probably means it isn't rclone's problem if uplink doesn't work. Would you agree?

Yes, that VM can't connect with 34.89.57.123:7777 but they have the same firewall rules. Sorcery.

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