Finding out which file failed to transfer

Help and Support
1

What is the problem you are having with rclone?

When an error happens during a file transfer, which I understand is most likely due to the file being modified as it's transfered, the logs give what appears to be the encrypted filename. This makes it difficult to figure out which file is causing the error. Searching for a file with a file size near the reported file size hasn't been successful.

In the logs below, the file is reported as '0vh0a5t3t5ohi2rr1r6lgijsugib9s6hvunsabttivvgqk8ejt3g'. Is there a way to get the filename?

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

rclone v1.60.1-DEV

  • os/version: debian 12.0 (64 bit)
  • os/kernel: 6.1.0-9-amd64 (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.19.8
  • go/linking: dynamic
  • go/tags: none

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

Backblaze

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

/usr/bin/rclone sync /bkup backblazeenc:bkup --bwlimit 1024k --links --transfers 32 --retries 16 --stats-one-line --log-level DEBUG --delete-excluded --one-file-system --b2-hard-delete

The rclone config contents with secrets removed.

[backblaze]
type = b2
account = XXXX
key = XXXX
endpoint =

[backblazeenc]
type = crypt
remote = backblaze:rclone-main
filename_encryption = standard
password = XXXX
password2 =

A log from the command with the -vv flag

2023/07/25 00:59:26 DEBUG : 0vh0a5t3t5ohi2rr1r6lgijsugib9s6hvunsabttivvgqk8ejt3g: Clearing upload URL because of error: Post "https://pod-000-1121-16.backblaze.com/b2api/v1/b2_upload_file/f1909637247605466b5a0015/c002_v0001121_t0017": net/http: HTTP/1.x transport connection broken: http: ContentLength=193905098 with Body length 193906178
2023/07/25 00:59:26 DEBUG : pacer: low level retry 1/1 (error Post "https://pod-000-1121-16.backblaze.com/b2api/v1/b2_upload_file/f1909637247605466b5a0015/c002_v0001121_t0017": net/http: HTTP/1.x transport connection broken: http: ContentLength=193905098 with Body length 193906178)
2023/07/25 00:59:26 DEBUG : .xsession-errors: Received error: Post "https://pod-000-1121-16.backblaze.com/b2api/v1/b2_upload_file/f1909637247605466b5a0015/c002_v0001121_t0017": net/http: HTTP/1.x transport connection broken: http: ContentLength=193905098 with Body length 193906178 - low level retry 1/10
2023/07/25 00:59:26 DEBUG : .xsession-errors: Computing sha1 hash of encrypted source
2

You can use rclone cryptdecode

rclone cryptdecode backblazeenc: 0vh0a5t3t5ohi2rr1r6lgijsugib9s6hvunsabttivvgqk8ejt3g

PS. You should update your rclone to the latest version:

rclone selfupdate --stable

3

Thanks! The command revealed the file was .xsession-errors, which it turns out was listed in the log file after all (I thought it was some sort of internal rclone/backblaze id, although now I'm not sure why I thought that).

Looks like the recently released Debian Bookworm still has an old version of rclone. I was used to maintaining my own copy of rclone on the previous version, looks like I'll have to do it again!

4

Yes most linux repos for some reason are never up to date with rclone. But as rclone is stand-alone binary without any dependencies there is no really any benefit of using outdated repository version. And thx to selfupdate option it is not much work maintaining the latest version.

what I always do is ensure that repo version is gone:

sudo apt remove rclone

install the latest from rclone direct:

sudo -v ; curl https://rclone.org/install.sh | sudo bash

and then periodically run:

sudo rclone selfupdate --stable
5

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