Will not syncronise files greater than 300k

[Ian Clarke]

I am using BestSync on a few computers and on one server that is operating on MSserver 2008, Bestsync will not syncronise files greater than about 300k. I have tried the same files from another server on a different site and they transfer to our FTP site without problems. On the problem machine, the file is transferred correctly but BestSync does not appear to receive the "File successfully transferred" I have taken a screen shot of the transfer process and it shows the response. For the 184k and 278k files, everything is fine. However, the response for the 350k file is missing and Bestsync appears to issue the MFMT command before it has received the response for the STOR command. Then is appears to screw up the connection and all other commands are not responded to.

Any thoughts for the cause of the problem.

[attachment=0]BestSync log.JPG[/attachment]

[RiseFly]

Is it possible that you send us (risefly(a)risefly.com) a test account, so that we can debug the problem?

[Ian Clarke]

Ok. The problem is not quite as it appeared. I found that the problem occured mostly with files of about 300kb. However, most small files and larger files are ok.

I upgraded from version 2013 to the latest Bestsync 2014 and now the problem is more apparrent. It apears that I am getting frequent Winsock errors and this may be the cause of the problem. The winsock errors were not being reported in version 2013.

So now, I have two problems:

1. What is causing the Winsock errors? They are worse if I set the task to have unlimited upload bandwidth.

2. If I do not limit the upload bandwidth, I see the winsock error when Bestsync checks for existing files (I do not get the error with unlimited bandwidth). Because of the error, Bestsync then decides that there are no files on my ftp server and so reports that all files need to be uploaded. This is obviously wrong and surely if there was an error and Bestsync cannot connect to the FTP site, it should not assume that the files are not there. I have attached two logs. The first is with unlimited bandwidth and Bestsync correctly reports that all files are sybcronised. The second is with the upload bandwidth limited to 512k. This log shows the error and then Bestsync wants to resyncronise all files again.



****** Preview log for no upload limit ***********
<220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
<220-You are user number 2 of 50 allowed.
<220-Local time is now 14:33. Server port: 21.
<220-This is a private system - No anonymous login
<220 You will be disconnected after 15 minutes of inactivity.
>USER xxx@xxx.net
<331 User xxx@xxx.net OK. Password required
>PASS *****
<230 OK. Current restricted directory is /
>TYPE I
<200 TYPE is now 8-bit binary
>OPTS UTF8 ON
<504 Unknown command
Begin to detect functions of FTP server.
>CWD /Calibration Certificates
<250 OK. Current directory is /Calibration Certificates
>CWD /Calibration Certificates/France
<250 OK. Current directory is /Calibration Certificates/France
>FEAT
<211-Extensions supported:
< EPRT
< IDLE
< MDTM
< SIZE
< MFMT
< REST STREAM
< MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
< MLSD
< AUTH TLS
< PBSZ
< PROT
< ESTA
< PASV
< EPSV
< SPSV
< ESTP
<211 End.
>TYPE A
<200 TYPE is now ASCII
>PASV
<227 Entering Passive Mode (69,90,162,130,32,161)
>MLSD
<150 Accepted data connection
<226-Options: -a -l
<226 5 matches total
/Calibration Certificates/France/tmpmdmt.htm
>TYPE I
<200 TYPE is now 8-bit binary
>PASV
<227 Entering Passive Mode (69,90,162,130,71,173)
>STOR tmpmdmt.htm
<150 Accepted data connection
<226-File successfully transferred
<226 0.115 seconds (measured here), 407.60 bytes per second
>TYPE A
<200 TYPE is now ASCII
>PASV
<227 Entering Passive Mode (69,90,162,130,132,121)
>MLSD
<150 Accepted data connection
<226-Options: -a -l
<226 6 matches total
Use the specified timezone (0) minutes.
>MDTM tmpmdmt.htm
<213 20131114133326
>MDTM 20131114133327 tmpmdmt.htm
<550 Can't check for file existence
>MFMT 20131114133327 tmpmdmt.htm
<213 UTIME OK
>MDTM tmpmdmt.htm
<213 20131114133327
>SITE UTIME 201311141333 tmpmdmt.htm
<213 UTIME OK
>MDTM tmpmdmt.htm
<213 20131114133300
>TYPE I
<200 TYPE is now 8-bit binary
>PASV
<227 Entering Passive Mode (69,90,162,130,26,159)
>REST 1
<350 Restarting at 1
>RETR tmpmdmt.htm
<150 Accepted data connection
<226-File successfully transferred
<226 0.000 seconds (measured here), 199.59 Kbytes per second
/Calibration Certificates/France/tmpmdmt.htm
>DELE tmpmdmt.htm
<250 Deleted tmpmdmt.htm
End detect server functions.
>TYPE A
<200 TYPE is now ASCII
>PASV
<227 Entering Passive Mode (69,90,162,130,206,150)
>MLSD
<150 Accepted data connection
<226-Options: -a -l
<226 5 matches total
>CWD /Calibration Certificates/France/Standard
<250 OK. Current directory is /Calibration Certificates/France/Standard
>PASV
<227 Entering Passive Mode (69,90,162,130,153,95)
>MLSD
<150 Accepted data connection
<226-Options: -a -l
<226 16 matches total
>CWD /Calibration Certificates/France/Standard/Cal2001
<250 OK. Current directory is /Calibration Certificates/France/Standard/Cal2001
>PASV
<227 Entering Passive Mode (69,90,162,130,149,105)
>MLSD
<150 Accepted data connection
<226-Options: -a -l
<226 469 matches total
>CWD /Calibration Certificates/France/Standard/Cal2006
<250 OK. Current directory is /Calibration Certificates/France/Standard/Cal2006
>PASV
<227 Entering Passive Mode (69,90,162,130,165,103)
>MLSD
<150 Accepted data connection
<226-Options: -a -l
<226 347 matches total


****** Preview log for no upload limit ***********
Note all the same as above except for the end of the log:

>CWD /Calibration Certificates/France/Standard
<250 OK. Current directory is /Calibration Certificates/France/Standard
>PASV
<227 Entering Passive Mode (69,90,162,130,46,5)
>MLSD
<150 Accepted data connection
<226-Options: -a -l
<226 16 matches total
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
winsock:Receive::Error.:error:(0x0000271e):Le système a détecté une adresse de pointeur non valide en essayant d’utiliser un argument pointeur dans un appel.
ReceiveData timeout.
<No list data.