Rclone mount with Dropbox, not responses

What is the problem you are having with rclone?

I tried rclone mount with Dropbox. It seems to be running forever and returns no responses.

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

I'm using a university computer cluster where I cannot install the latest rclone. I'm just wondering if the error is related to the version.

rclone v1.57.0-DEV

  • os/version: almalinux 8.7 (64 bit)
  • os/kernel: 4.18.0-425.13.1.el8_7.x86_64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.16.12
  • go/linking: dynamic
  • go/tags: none

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

Dropbox

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

rclone mount --vfs-cache-mode full remote:/test ./dropbox/test/ 

The rclone config contents with secrets removed.

[remote]
type = dropbox
client_id = xxxxx
client_secret = xxxxx
token = {"access_token":"xxx",
"token_type":"bearer",
"refresh_token":"xxx",
"expiry":"xxx"}

A log from the command with the -vv flag

There was no log generated.

In v1.59.0 we migrated from the deprecated dropbox API - it might be that they've turned it off now.

Rclone doesn't need any kind of installation - if you can copy the binary to your home directory you can run it from there.

Hi @ncw , thanks for your suggestion! I've downloaded rclone v1.62.0 and it still didn't response.

rclone v1.62.0

  • os/version: almalinux 8.7 (64 bit)
  • os/kernel: 4.18.0-425.13.1.el8_7.x86_64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.20.2
  • go/linking: static
  • go/tags: none

Does rclone lsf remote:/test work?

If not run it with -vv --dump bodies and post the output.

Yes, rclone lsf remote:/test works.

You'll need to be more specific with this.

What exactly happens?

Can you paste a log generated with -vv?

what do you mean by no responses?

note: to access the files in ./dropbox/test/ , the rclone mount command has to be running.
does ls ./dropbox/test/ list the files?

to the mount command, add -vv and post the output from the terminal

Sorry, I don't know the --vv option. Below is the log:

2023/03/15 10:42:38 DEBUG : rclone: Version "v1.62.0" starting with parameters ["/home/s/ssun226/rclone" "mount" "remote:/test/" "/home/dropbox/test/" "-vv"]
2023/03/15 10:42:38 DEBUG : Creating backend with remote "remote:/test/"
2023/03/15 10:42:38 DEBUG : Using config file from "/home/s/ssun226/.config/rclone/rclone.conf"
2023/03/15 10:42:39 DEBUG : Dropbox root '': Using root namespace "196693667"
2023/03/15 10:42:39 DEBUG : fs cache: renaming cache item "remote:/test/" to be canonical "remote:test"
2023/03/15 10:42:40 DEBUG : Dropbox root 'test': Mounting on "/home/dropbox/test/"
2023/03/15 10:42:40 DEBUG : : Root: 
2023/03/15 10:42:40 DEBUG : : >Root: node=/, err=<nil>
2023/03/15 10:42:41 DEBUG : /: Attr: 
2023/03/15 10:42:41 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxrwx---, err=<nil>
2023/03/15 10:43:00 DEBUG : /: Attr: 
2023/03/15 10:43:00 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxrwx---, err=<nil>
2023/03/15 10:43:02 DEBUG : /: Attr: 
2023/03/15 10:43:02 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxrwx---, err=<nil>

Thanks for the post. Sorry I didn't know the -vv option. ls ./dropbox/test/ list the files. And I posted the log in the previous post.

ok, looks good. working as expected.

is there anything else you need help with?

It reported an error message after 10 minutes.

2023/03/15 11:37:44 DEBUG : Dropbox root 'test': Checking for changes on remote
2023/03/15 11:41:57 INFO  : Signal received: interrupt
2023/03/15 11:41:57 INFO  : Dropbox root 'test': Committing uploads - please wait...
2023/03/15 11:41:57 ERROR : /home/dropbox/test: Unmounted rclone mount
2023/03/15 11:41:57 INFO  : Exiting...

did you manually kill the rclone mount command?

can you post the top 20 lines of the debug log?

That's what happens you hit control c or log out.

I did hit enter on the command window. Maybe that killed the command? I've re-entered the rclone mount -vv remote:/test/ ~/dropbox/test command and the log is as below.

2023/03/15 11:44:53 DEBUG : Creating backend with remote "remote:/test/"
2023/03/15 11:44:53 DEBUG : Using config file from "/home/.config/rclone/rclone.conf"
2023/03/15 11:44:54 DEBUG : Dropbox root '': Using root namespace "196693667"
2023/03/15 11:44:54 DEBUG : fs cache: renaming cache item "remote:/test/" to be canonical "remote:test"
2023/03/15 11:44:55 DEBUG : Dropbox root 'test': Mounting on "/home/dropbox/test"
2023/03/15 11:44:55 DEBUG : : Root: 
2023/03/15 11:44:55 DEBUG : : >Root: node=/, err=<nil>
2023/03/15 11:45:55 DEBUG : Dropbox root 'test': Checking for changes on remote
2023/03/15 11:50:57 DEBUG : Dropbox root 'test': Checking for changes on remote
2023/03/15 11:56:07 DEBUG : Dropbox root 'test': Checking for changes on remote
2023/03/15 12:01:28 DEBUG : Dropbox root 'test': Checking for changes on remote
2023/03/15 12:06:31 DEBUG : Dropbox root 'test': Checking for changes on remote
2023/03/15 12:11:55 DEBUG : Dropbox root 'test': Checking for changes on remote

if you want to have rclone run in the background,
try --daemon, cron, systemd, tmux/screen

I see. Thanks! It seemed that it took too long for rclone to mount dropbox on my drive. This is the log after 30 minutes

Will do and update it here. Thanks! Yesterday after 3 hours I still couldn't get a single folder in dropbox mounted. I'm afraid there might be a bottleneck somewhere.

There's no issues with that log at all so not sure there is any bottleneck.

Did you copy something?

I think you are confused.

It's not a forking process, it won't return anything to you.

You normally run things like this as a service / daemon / etc.

Yes, I was copying log and that killed the process. I tried ~/rclone mount remote:/test/ ~/dropbox/test/ -vv
and the command window was stuck with

DEBUG : Dropbox root 'test': Checking for changes on remote

for 1 hour. So I ran instead ~/rclone mount --poll-interval 0 remote:/test/ ~/dropbox/test/ -vv then the command window provided no updates for more than 4 hours. I checked the local folder, the remote one didn't get mounted. This is what I meant it didn't return anything. It seems that the process is stuck somewhere.

2023/03/15 15:25:32 DEBUG : rclone: Version "v1.62.0" starting with parameters ["/homerclone" "mount" "--poll-interval" "0" "remote:/test/" "/homedropbox/test/" "-vv"]
2023/03/15 15:25:32 DEBUG : Creating backend with remote "remote:/test/"
2023/03/15 15:25:32 DEBUG : Using config file from "/home.config/rclone/rclone.conf"
2023/03/15 15:25:33 DEBUG : Dropbox root '': Using root namespace "196693667"
2023/03/15 15:25:33 DEBUG : fs cache: renaming cache item "remote:/test/" to be canonical "remote:test"
2023/03/15 15:25:33 DEBUG : Dropbox root 'test': Mounting on "/homedropbox/test/"
2023/03/15 15:25:33 DEBUG : : Root: 
2023/03/15 15:25:33 DEBUG : : >Root: node=/, err=<nil>