Hi all,
I frequently get the error:
Die Datei "gdrive:\xxx\BackupFull.zip" kann nicht geschrieben werden.
CURLE_SEND_FAIL_REWIND: Recv failure: Connection was reset [curl_easy_perform]
The file is about 3GB in size and the error does not occur every day. Upload bandwidth is 10Mbit/s. FreeFileSync version is current. Any ideas?
Many thanks,
Markus
Error CURLE_SEND_FAIL_REWIND during Gdrive upload
- Posts: 3
- Joined: 3 Apr 2023
-
- Site Admin
- Posts: 7506
- Joined: 9 Dec 2007
Does this error occur right at the beginning of copying the 3GB file, or later after a large part of it has already been uploaded?
- Posts: 3
- Joined: 3 Apr 2023
From the time that has passed since the start of the backup I'd suppose it happens more towards the end of the transfer:
01:55:48
Aktualisiere Datei "gdrive:\xxxBackupFull.zip"
02:18:16
Die Datei "gdrive:\xxxBackupFull.zip" kann nicht geschrieben werden.
CURLE_SEND_FAIL_REWIND: Recv failure: Connection was reset [curl_easy_perform]
So the error occurs abt. 23mins after the start of the transfer.
Best,
Markus
01:55:48
Aktualisiere Datei "gdrive:\xxxBackupFull.zip"
02:18:16
Die Datei "gdrive:\xxxBackupFull.zip" kann nicht geschrieben werden.
CURLE_SEND_FAIL_REWIND: Recv failure: Connection was reset [curl_easy_perform]
So the error occurs abt. 23mins after the start of the transfer.
Best,
Markus
-
- Site Admin
- Posts: 7506
- Joined: 9 Dec 2007
From the error message one can deduce that first "CURLE_RECV_ERROR: Recv failure: Connection was reset" happened.
Then apparently libcurl tries to *retry* the upload , which requires the input stream to be reset. FFS does not implement the corresponding callback, so libcurl fails with CURLE_SEND_FAIL_REWIND.
My guess is that the root problem is an unstable connection to Google, which matches the symptoms that the problem only happens occasionally.
Solution? Implementing the input stream reset function in FreeFileSync seems like a bad idea, because it would hide the fact that the connection broke. Although the upload might succeed eventually, the upload time may double every now and then without any error indication. FFS on the other hand already has retry functionality. So the best solution would be to set up "automatic retry", so that connection issues will be at least logged.
Then apparently libcurl tries to *retry* the upload , which requires the input stream to be reset. FFS does not implement the corresponding callback, so libcurl fails with CURLE_SEND_FAIL_REWIND.
My guess is that the root problem is an unstable connection to Google, which matches the symptoms that the problem only happens occasionally.
Solution? Implementing the input stream reset function in FreeFileSync seems like a bad idea, because it would hide the fact that the connection broke. Although the upload might succeed eventually, the upload time may double every now and then without any error indication. FFS on the other hand already has retry functionality. So the best solution would be to set up "automatic retry", so that connection issues will be at least logged.
- Posts: 3
- Joined: 3 Apr 2023
Thanks for coming back to me so quickly!
I cannot completely rule out that my setup has instabilities with such relatively large uploads. I could split my backup file to reduce the transfer time per file. A desperate attempt ;-)
I cannot find any setting for 'automatic retry' - is this user defineable?
I cannot completely rule out that my setup has instabilities with such relatively large uploads. I could split my backup file to reduce the transfer time per file. A desperate attempt ;-)
I cannot find any setting for 'automatic retry' - is this user defineable?
