From Mega to Dropbox/gdrive getting error connection reset by peer

Suspected Bug
1

What is the problem you are having with rclone?

I have 300GB+ files in Mega but during transferring to Gdrive/Dropbox (some files got transferred) but for remaining(almost 14GB) it is showing error connection reset by peer.
Same problem in gdrive and dropbox.

What is your rclone version (output from rclone version)

1.53.1

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Linux Ubuntu

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

Mega to gdrive/dropbox

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

rclone copy mga:"My Mega" dbox:MyMega -vvP

The rclone config contents with secrets removed.

[dbox]
type = dropbox
token = {"mytoken","token_type":"bearer","expiry":"0001-01-01T00:00:00Z"}

[mga]
type = mega
user = mygmail
pass = mypass

A log from the command with the -vv flag

2020/10/07 10:08:18 DEBUG : pacer: low level retry 7/10 (error Post "https://content.dropboxapi.com/2/files/upload_session/start": read tcp 172.17.0.2:50578->89.44.168.245:80: read: connection reset by peer)
2020/10/07 10:08:19 DEBUG : 1) Maths/Gagan(1-68)/day-62  Algebra-7.mp4: Reopening on read failure after 0 bytes: retry 7/10: read tcp 172.17.0.2:50740->89.44.168.245:80: read: connection reset by peer
2020/10/07 10:08:20 DEBUG : 1) Maths/Gagan(1-68)/day-62  Algebra-7.mp4: Reopening on read failure after 0 bytes: retry 8/10: read tcp 172.17.0.2:50760->89.44.168.245:80: read: connection reset by peer
2020/10/07 10:08:20 DEBUG : pacer: low level retry 3/10 (error Post "https://content.dropboxapi.com/2/files/upload_session/start": read tcp 172.17.0.2:50628->89.44.168.245:80: read: connection reset by peer)
2020/10/07 10:08:21 DEBUG : 1) Maths/Gagan(1-68)/day-62  Algebra-7.mp4: Reopening on read failure after 0 bytes: retry 9/10: read tcp 172.17.0.2:50776->89.44.168.245:80: read: connection reset by peer

And this error is repeating.

P.S: One thing I noticed while copying is that while showing progress at first it shows like

Transferred: 5.366G / 29.343 GBytes, 18%, 18.347 MBytes/s, ETA 22m18s` Checks: 2321 / 2321, 100%` Transferred: 19 / 94, 20%` Elapsed time: 4m59.4s` Transferring:

But after some transaction ###TOTAL SIZE DECREASED :astonished: (from 29.343 to 28.892)

Transferred: 13.412G / 28.892 GBytes, 46%, 4.977 MBytes/s, ETA 53m4s` Errors: 3 (retrying may help)` Checks: 2321 / 2321, 100%` Transferred: 43 / 91, 47%` Elapsed time: 45m59.4s` Transferring:

2

I would say that is probably Mega rate limiting you...

You could try adding a --tpslimit to your command to slow rclone down a bit.

Unexpected! I think (not 100% sure) this is caused by the errors taking the transfers out of the queue, but since they haven't been transferred the total goes down.

3

I have 12TB mega transfer limit.

And then I tried with the same file using multcloud free account and those files are not getting transferred from there too.

And for error they gave reason like

Error: Insufficient data written.

Solution: MediaFire needs to know the file size before saving it. When processing the file, the real file size has to be the same as the predicted. Otherwise, it will fail. You can use another cloud drive to transfer the file, please try the following steps:
1. Transfer the file to another cloud drive;
2. Transfer that file from the other cloud drive to MediaFire.

As I am using Dropbox and google drive...no mediafire

But This error makes sense as you can see that size decreased over time means size is not being read correctly from mega.
But I can Download those files from mega app.

4

Can you tell me the appropriate value of --tpslimit so I can try?:confused:

5

Try --tpslimit 5 - make the number smaller if it still fails or if it works perfectly make it larger until it fails.

6

Not worked..not even a single byte is getting transferred now😕

7

I think you've probably been locked out by mega. Waiting a few hours or 24 hours will restore your account.

1 Like
8

Okay sir...I will report after two days.:hugs:
Thanks :relieved:

1 Like
9

Yeah...That was the reason I guess.:astonished:

Because today it started copying again.

But the total file size is still decreasing :hugs:

1 Like
10

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