RCLONE sync with Citrix Sharefile

Help and Support
1

What is the problem you are having with rclone?

corrupted on transfer. md5 hash differ

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

rclone v1.61.1

  • os/version: Microsoft Windows 10 Pro 21H2 (64 bit)
  • os/kernel: 10.0.19044.2604 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.19.4
  • go/linking: static
  • go/tags: cmount

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

Citrix Sharefile

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

C:\Program Files\rclone.ccbamatx>rclone sync -i sharefile: c:\data\share1\ --sharefile-root-folder-id "allshared"

The rclone config contents with secrets removed.


Editing existing "sharefile" remote with options:
- type: sharefile
- root_folder_id: allshared
- endpoint: https://XXXXX.sharefile.com
- token: {"access_token":"XXXXX","token_type":"bearer","refresh_token":"XXXXXx4XXXXX","expiry":"2023-03-02T03:49:35.8059387-06:00"}

Option root_folder_id.
ID of the root folder.
Leave blank to access "Personal Folders".  You can use one of the
standard values here or any folder ID (long hex number ID).
Choose a number from below, or type in your own string value.
Press Enter for the default (allshared).

A log from the command with the -vv flag

Here is the TAIL of the log output.......

2023/03/01 20:14:00 DEBUG : Local file system at //?/c:/data/share1: Waiting for checks to finish
2023/03/01 20:14:00 DEBUG : Local file system at //?/c:/data/share1: Waiting for transfers to finish
2023/03/01 20:14:57 NOTICE:
Transferred:              0 B / 536.161 MiB, 0%, 0 B/s, ETA -
Checks:                80 / 80, 100%
Transferred:            0 / 216, 0%
Elapsed time:       1m0.0s
Transferring:
 *                     Test Folder/TuPayFU.fmp12: transferring
 * Board Meetings/2022/He…rd Meeting 2022.08.zip: transferring
 * Board Meetings/2022/He…ard Packet 2022.01.pdf: transferring
 * Board Meetings/2022/He…ard Packet 2022.02.pdf: transferring

2023/03/01 20:15:57 NOTICE:
Transferred:              0 B / 536.161 MiB, 0%, 0 B/s, ETA -
Checks:                80 / 80, 100%
Transferred:            0 / 216, 0%
Elapsed time:       2m0.0s
Transferring:
 *                     Test Folder/TuPayFU.fmp12: transferring
 * Board Meetings/2022/He…rd Meeting 2022.08.zip: transferring
 * Board Meetings/2022/He…ard Packet 2022.01.pdf: transferring
 * Board Meetings/2022/He…ard Packet 2022.02.pdf: transferring

2023/03/01 20:16:57 NOTICE:
Transferred:              0 B / 536.161 MiB, 0%, 0 B/s, ETA -
Checks:                80 / 80, 100%
Transferred:            0 / 216, 0%
Elapsed time:       3m0.0s
Transferring:
 *                     Test Folder/TuPayFU.fmp12: transferring
 * Board Meetings/2022/He…rd Meeting 2022.08.zip: transferring
 * Board Meetings/2022/He…ard Packet 2022.01.pdf: transferring
 * Board Meetings/2022/He…ard Packet 2022.02.pdf: transferring

2023/03/01 20:17:57 NOTICE:
Transferred:              0 B / 536.161 MiB, 0%, 0 B/s, ETA -
Checks:                80 / 80, 100%
Transferred:            0 / 216, 0%
Elapsed time:       4m0.0s
Transferring:
 *                     Test Folder/TuPayFU.fmp12: transferring
 * Board Meetings/2022/He…rd Meeting 2022.08.zip: transferring
 * Board Meetings/2022/He…ard Packet 2022.01.pdf: transferring
 * Board Meetings/2022/He…ard Packet 2022.02.pdf: transferring

2023/03/01 20:18:57 NOTICE:
Transferred:              0 B / 536.161 MiB, 0%, 0 B/s, ETA -
Checks:                80 / 80, 100%
Transferred:            0 / 216, 0%
Elapsed time:       5m0.0s
Transferring:
 *                     Test Folder/TuPayFU.fmp12: transferring
 * Board Meetings/2022/He…rd Meeting 2022.08.zip: transferring
 * Board Meetings/2022/He…ard Packet 2022.01.pdf: transferring
 * Board Meetings/2022/He…ard Packet 2022.02.pdf: transferring
2

hi, did not see that in the log snippet?

3

Yes... I just noticed that.... it seems like the error changes when we add the -vv

So... before we added the -vv, we got the hash error.

After we added the -vv... we started getting the errors at the tail of the log

4

ok, need to reproduce the issue.

use a debug log, not snippets from terminal.
--log-level=DEBUG --log-file=c:\path\to\rclone.log

5

I've noticed this as well, ShareFile converts the hash into their own format (It has dashes and other values in it). I've had to use --ignore-checksum, or it errors every time.

6

Ahhhh. will try that.... and will build the log. thanks.

7

I don't think share file should be doing this. I'd love to see a debug log around the error.

8

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