Dropbox upload stuck at Committing uploads

Help and Support
1

STOP and READ USE THIS TEMPLATE NO EXCEPTIONS - By not using this, you waste your time, our time and really hate puppies. Please remove these two lines and that will confirm you have read them.

What is the problem you are having with rclone?

I have a couple raspberry pi's attempting to upload some data to dropbox but they recently have been having trouble uploading to dropbox and seem to stop at "Committing uploads - please wait...".

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

rclone v1.64.2
- os/version: raspbian 11.8 (64 bit)
- os/kernel: 6.1.21-v8+ (aarch64)
- os/type: linux
- os/arch: arm64 (ARMv8 compatible)
- go/version: go1.21.3
- go/linking: static
- go/tags: none

Are you on the latest version of rclone? You can validate by checking the version listed here: Rclone downloads
-->

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

Dropbox

rclone copy -vv /home/pi/Desktop/google_drive dropbox:${dropboxPath}/${dataFolder} --check-first --log-file=/home/pi/Desktop/rclone_log_files/${rfilename}.txt
rclone check -vv /home/pi/Desktop/google_drive dropbox:${dropboxPath}/${dataFolder}  --differ /home/pi/Desktop/rclone_log_files/nonmatch.txt --log-file=/home/pi/Desktop/rclone_log_files/${rfilename}.txt

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

[dropbox]
type = dropbox
token = XXX
### Double check the config for sensitive info before posting publicly

A log from the command that you were trying to run with the -vv flag

2023/10/24 23:17:27 DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "copy" "-vv" "/home/pi/Desktop/google_drive" "dropbox:FieldData/test3" "--check-first" "--log-file>2023/10/24 23:17:27 DEBUG : Creating backend with remote "/home/pi/Desktop/google_drive"
2023/10/24 23:17:27 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2023/10/24 23:17:27 DEBUG : Creating backend with remote "dropbox:FieldData/test3"
2023/10/24 23:17:28 INFO  : Dropbox root 'FieldData/test3': Running all checks before starting transfers
2023/10/24 23:17:28 DEBUG : temp_data/temp_10-22-2023_22:19:18.txt: Size and modification time the same (differ by -426.385061ms, within tolerance 1s)
2023/10/24 23:17:28 DEBUG : temp_data/temp_10-22-2023_22:19:18.txt: Unchanged skipping
2023/10/24 23:17:28 DEBUG : Dropbox root 'FieldData/test3': Waiting for checks to finish
2023/10/24 23:17:28 DEBUG : pni_data/pni_rm3100_10-22-2023_22:19:18.txt: Size and modification time the same (differ by -330.553566ms, within tolerance 1s)
2023/10/24 23:17:28 DEBUG : pni_data/pni_rm3100_10-22-2023_22:19:18.txt: Unchanged skipping
2023/10/24 23:17:28 INFO  : Dropbox root 'FieldData/test3': Checks finished, now starting transfers
2023/10/24 23:17:28 DEBUG : Dropbox root 'FieldData/test3': Waiting for transfers to finish
2023/10/24 23:17:28 INFO  : There was nothing to transfer
2023/10/24 23:17:28 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Checks:                 2 / 2, 100%
Elapsed time:         1.2s

2023/10/24 23:17:28 DEBUG : 7 go routines active
2023/10/24 23:17:28 INFO  : Dropbox root 'FieldData/test3': Committing uploads - please wait...
2023/10/24 23:17:28 DEBUG : rclone: Version "v1.64.2" starting with parameters ["rclone" "check" "-vv" "/home/pi/Desktop/google_drive" "dropbox:FieldData/test3" "--differ" "/home/pi/Deskt>2023/10/24 23:17:28 DEBUG : Creating backend with remote "/home/pi/Desktop/google_drive"
2023/10/24 23:17:28 DEBUG : Using config file from "/root/.config/rclone/rclone.conf"
2023/10/24 23:17:28 DEBUG : Creating backend with remote "dropbox:FieldData/test3"
2023/10/24 23:17:29 INFO  : Using dropbox for hash comparisons
2023/10/24 23:17:29 DEBUG : Dropbox root 'FieldData/test3': Waiting for checks to finish
2023/10/24 23:17:29 DEBUG : temp_data/temp_10-22-2023_22:19:18.txt: dropbox = 9a540e118cb15bf6d52469b2a2e631566a736b3146b7d5c7a246ec9fc0f700ab OK
2023/10/24 23:17:29 DEBUG : temp_data/temp_10-22-2023_22:19:18.txt: OK
2023/10/24 23:17:30 DEBUG : pni_data/pni_rm3100_10-22-2023_22:19:18.txt: dropbox = 75433d687caad2cc0718d8461a46fc5ac7f9e0c60ce7165fc974999f8d7c46e2 OK
2023/10/24 23:17:30 DEBUG : pni_data/pni_rm3100_10-22-2023_22:19:18.txt: OK
2023/10/24 23:17:30 NOTICE: Dropbox root 'FieldData/test3': 0 differences found
2023/10/24 23:17:30 NOTICE: Dropbox root 'FieldData/test3': 2 matching files
2023/10/24 23:17:30 INFO  :
Transferred:              0 B / 0 B, -, 0 B/s, ETA -
Checks:                 2 / 2, 100%
Elapsed time:         1.2s

2023/10/24 23:17:30 DEBUG : 8 go routines active
2023/10/24 23:17:30 INFO  : Dropbox root 'FieldData/test3': Committing uploads - please wait...
2

If you let it run for longer does it complete?

If it doesn't complete after a few minutes, try kill -QUIT the process and post the backtrace generated here.

3

It did not end up finishing in a couple minutes but I am having trouble locating the backtrace when I try to kill it. This command is called in a script called sync.sh. Do I run ./sync.sh then run kill -QUIT before it finishes?
This i what I tried to do

pi@test2:~/Desktop $ sudo ./sync.sh
kill -QUIT
pi@test2:~/Desktop $ kill -QUIT
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
4

What you need to do is find the process id of rclone so ps ax | grep rclone should show it. Then use that number with the kill, so kill -QUIT 12345

That should stop rclone and make the backtrace.

5

So it looks like it did end up finishing as there was nothing to kill but there are no files in dropbox.

6

What did the log say?

8

Sorry it took my a couple days to reply, had trouble how to get the files.

This also isnt the entire log because it was way too big for pastebin, but just a some of the beginning and some of the end

9

I don't see the backtrace from the kill -QUIT - that is the bit I need.

It looks like this and may be 100s or 1000s of lines long

SIGQUIT: quit
PC=0x10a21a1 m=0 sigcode=128

goroutine 0 [idle]:
runtime.futex()
	/opt/go/go1.21/src/runtime/sys_linux_amd64.s:557 +0x21 fp=0x7fff9d48be88 sp=0x7fff9d48be80 pc=0x10a21a1
runtime.futexsleep(0x279c6b3?, 0x9d48bf08?, 0x1077607?)
	/opt/go/go1.21/src/runtime/os_linux.go:69 +0x30 fp=0x7fff9d48bed8 sp=0x7fff9d48be88 pc=0x1063c90
runtime.notesleep(0x49c34a8)
	/opt/go/go1.21/src/runtime/lock_futex.go:160 +0x87 fp=0x7fff9d48bf10 sp=0x7fff9d48bed8 pc=0x10392a7
runtime.mPark(...)
	/opt/go/go1.21/src/runtime/proc.go:1632
runtime.stopm()
	/opt/go/go1.21/src/runtime/proc.go:2536 +0x8c fp=0x7fff9d48bf40 sp=0x7fff9d48bf10 pc=0x106f18c
runtime.findRunnable()
...
10
11

It has completed the copy by the look of the trace and now it is doing the rclone check.

Remember it will have to read all the data from disk and hash it to do the check so that can take some time. Every 1 minute you should see some stats being printed (adjust the time with --stats 10s).

12

Should I still kill it and then provide the trace? Or add the --stats 10s and let it run? Also should the files show up after the copy? There are still no files in dropbox

13

Try using rclone lsf to see the files.

I suspect they've ended up somewhere just not where you expected!

Did you get dropbox accounts mixed up when you did the oauth maybe?

14

I tried using rclone lsf to see if they appeared anywhere but they did not. I also just re setup the rclone config and reauthenticated but it still did not upload to the dropbox.

15

Try copying one file.

16

It works now when I run the script manually, but when I put the script in my crontab it does not upload

17

Is the crontab running as you? If not it will be using the wrong config file.

18

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