bestsync.us

I have a strange bug effect I believe.

SFTP error messages indicating a winsock overload/stall appear to be interpreted by Bestsync as SUCCESS and so the next file transfer is started. This immediately fails (but again shown as SUCCESS) and a cascade effect follows whereby 100% success is recorded but with a log full of errors ..and no files transfered.

I have made an avi recording of the GUI and preview log that is too large to upload so I am providing a dropbox link.

https://dl.dropboxusercontent.com/u/679 ... 016.10.avi


I am running Windows 7 release 8.0.5.9 64 bit version? The SFTP server is CrushFTP.

Thanks

Thank you for the video.
I see that only one file was failed due to the network failed to response.
This symptom may be normal, because the retry function of BestSync should be able to recover from this error.

Apologies
I'm not sure you are interpreting the log file in the way I am.
All files after the error occurs fail but are marked as success. Once marked success files are not retried. The error messages are quite clearly showing a fail but the file is still marked as success in the preview window and log.
This means that if a task is setup to monitor changes in the source only..the transfer will fail in a most dangerous way.
Thanks

If the result is "success", the file must be copied successfully. Though there is error in the log, the error may have been recovered.
Please confirm if the content of the target file is copied successfully.

Hi
That is indeed the problem.
I can confirm that the files marked success are not transferred at all. Not even an empty holder.
Thanks for looking into this.

Version 8.0.6.4 has fixed a problem related to this symptom.
Please download the new version to see if the problem has been fixed.