Large Dropbox-Box Transfer died

a continuation of Sanity check large dropbox -> box copy - #25 by ncw

rclone v1.62.2

  • os/version: ubuntu 18.04 (64 bit)

  • os/kernel: 4.15.0-208-generic (x86_64)

  • os/type: linux

  • os/arch: amd64

  • go/version: go1.20.2

  • go/linking: static

  • go/tags: none

a background team folder to team folder transfer is cranking away no issue, in the background doing user to user transfers (sequentially) and one of them froze up

rclone copy dropbox:/ "box:/User Folders/XXXX Personal Folder" --max-backlog 3400000 --dropbox-impersonate XXXXX --order-by size,desc --transfers 25 --log-file xxxxx-transfer.log --no-update-modtime --fast-list --ignore-checksum --size-only --checkers 30 --files-from-raw xxxx@invnt.com-diff.txt --dropbox-batch-mode sync -vvvP

Transferred: 6.525 TiB / 7.159 TiB, 91%, 0 B/s, ETA -
Errors: 36 (retrying may help)
Transferred: 29380 / 321247, 9%

eventually froze to 0 and stuck:

  • : 59% /46.908Mi, 0/s, 2562047h47m16s

bottom of debug log:

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : pacer: Rate limited, increasing sleep to 20ms

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : pacer: Rate limited, increasing sleep to 40ms

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : pacer: Rate limited, increasing sleep to 80ms

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : pacer: Rate limited, increasing sleep to 160ms

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : pacer: Rate limited, increasing sleep to 320ms

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : pacer: Rate limited, increasing sleep to 640ms

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : pacer: Rate limited, increasing sleep to 1.28s

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : pacer: Rate limited, increasing sleep to 2s

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:02:33 DEBUG : Couldn't decode error response: invalid character '<' looking for beginning of value

2023/04/12 06:02:33 DEBUG : pacer: low level retry 1/1 (error Error "502 Bad Gateway" (502))

2023/04/12 06:07:33 DEBUG : pacer: low level retry 1/1 (error Post "https://upload.box.com/api/2.0/files/content": read tcp 69.50.93.2:40442->74.112.186.128:443: i/o timeout)

2023/04/12 06:36:35 DEBUG : box root 'User Folders/XXXXX Personal Folder': Token expired but no uploads in progress - doing nothing

Looks like box.com had issues. Not much to do other than ask them or try again later.

hmmm this might be a good use case of --max-duration, is there another way to sort of catch this and kill the job ?

Not really as it will eventually time out on it's own but any flag really wouldn't do too much imo.

You'd want to check the logs I'd imagine and take action based on the logs.

1 Like

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